| Time |
Nick |
Message |
|---|
| 3:51 AM |
behmann |
can someone point me towards some documentation that identifies how to access items like packaging, groupid, version, etc from the pom in a custom plugin? |
| 3:52 AM |
ld |
behmann: I don't know where the docs are, but you can specify an ivar on your mojo and annotate it with the @parameter javadoc tag??? |
| 3:52 AM |
ld |
And specify an "expression" that evaluates to a POM value??? |
| 3:54 AM |
ld |
@parameter expression="${project.version}" |
| 3:54 AM |
ld |
for example |
| 3:54 AM |
behmann |
hmmm... |
| 3:56 AM |
ld |
Make sense? |
| 3:56 AM |
behmann |
yes, perfectly |
| 3:57 AM |
behmann |
and I've been using that feature to get access to the values set in the of my plugin |
| 3:57 AM |
behmann |
but I'm trying to get access to the value in the tag at the top of the pom (outside of my plugin config)... and do some action based on the packaging |
| 3:57 AM |
behmann |
and I'm trying to see if that is even possible |
| 3:58 AM |
ld |
behmann: items in configuration are injected based on the name of the ivar |
| 3:59 AM |
ld |
${project.packaging} should get you the packaging type. |
| 3:59 AM |
behmann |
ahhh |
| 4:00 AM |
ld |
Take everything I say with salt though, cause I have only learnt through trial and error |
| 4:01 AM |
behmann |
ahh, that did the trick :) |
| 4:01 AM |
behmann |
thank you VERY much |
| 4:01 AM |
ld |
No probs. |
| 5:15 AM |
aw |
I am having a problem getting some optional features of the dependency plugin to work... Specifically the resolve-plugins goal. For example: "mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:resolve-plugins" works. If I add: -DexcludeTransitive=true, that works. But if I add: -DoutputFile=blah.txt, NOTHING. Or specifying include/exclude logic parameters. What gives? |
| 5:28 AM |
aw |
Can anybody tell me how to get the following to work? "mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:resolve-plugins -DoutputFile=plugins.txt" The file isn't being created. |
| 5:37 AM |
aw |
mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:resolve-plugins -Dexclu |
| 5:37 AM |
aw |
deArtifactId=maven-ejb-plugin |
| 5:38 AM |
aw |
deArtifactId=maven-ejb-plugin |
| 5:38 AM |
aw |
deArtifactId=maven-ejb-plugin |
| 5:39 AM |
aw |
I can't seem to get the include/exclude features to have any effect either. For example: "mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:resolve-plugins -DexcludeArtifactId=maven-ejb-plugin" doesn't change the output. Am I missing something? |
| 5:57 AM |
aw |
I can't seem to get the include/exclude features to have any effect either. For example: "mvn org.apache.maven.plugins:maven-dependency-plugin:2.0:resolve-plugins -DexcludeArtifactId=maven-ejb-plugin" doesn't change the output. Am I missing something? |
| 9:11 AM |
darulez |
history |
| 11:56 AM |
gertv |
hi: is it possible to replace an @component with my own implementation? |
| 11:57 AM |
gertv |
I thought it would have been enough to create a components.xml and specify the correct in the pom.xml where I want to plug in the new implementation, but that doesn't work |
| 2:47 PM |
jMCg |
Hi folks, I've been debugging with wsmoak in #archiva a build of some in-house software: http://dpaste.com/50471/ |
| 2:48 PM |
wsmoak |
jMCg, see if this helps: http://docs.codehaus.org/display/MAVENUSER/Creating+JBoss+SAR+(Service+ARchive)+Artifacts |
| 2:48 PM |
jMCg |
It's installing a sar as jar, then looking for sar again. |
| 2:48 PM |
wsmoak |
seems to be exactly what you're trying to do :) |
| 3:15 PM |
pgier |
Brian: ping |
| 3:15 PM |
Brian |
pong |
| 3:15 PM |
pgier |
what do you think about this issue for 2.1? http://jira.codehaus.org/browse/MNG-3328 |
| 3:16 PM |
pgier |
actually, I should clarify the issue a little bit |
| 3:16 PM |
jMCg |
Maven makes my head spin... |
| 3:16 PM |
pgier |
because looking at it now, it doesn't maintain good backward compat |
| 3:16 PM |
jMCg |
And I'm saying this as somebody who's subscriebed to the libtool-users mailing list. |
| 3:17 PM |
pgier |
I'm thinking of using a syntax more like in MNG-1753 |
| 3:18 PM |
Brian |
pgier, looking |
| 3:18 PM |
pgier |
I guess my main question is whether it's ok to make model changes for 2.1 |
| 3:18 PM |
pgier |
hopefully not changing existing tags, just adding new ones |
| 3:19 PM |
Brian |
pgier, these changes should have a proposal written up and posted on the wiki (which is what brett was saying in his comment) |
| 3:19 PM |
pgier |
Ok, I can write something up in the proposal |
| 3:19 PM |
pgier |
then bring it up on the dev list? |
| 3:20 PM |
Brian |
yep |
| 3:20 PM |
pgier |
will there be a new model for 2.1? |
| 3:20 PM |
pgier |
something like 4.1.0? |
| 3:21 PM |
pgier |
Currently, I don't see anything marked as 4.1.0 in the maven-model trunk |
| 3:21 PM |
Brian |
pgier, it's up in the air but lots of stuff require it |
| 3:21 PM |
Brian |
there isn't a way to handle the model changes iirc |
| 3:22 PM |
Brian |
and then what that means to 2.0.x users trying to consume artifacts deployed with 2.1 etc... |
| 3:22 PM |
brett |
pgier: I've already done that successfully on a branch for the attributes, so I think we can do that. It's really in the repository that's a problem as if you start deploying new ones, artifacts can't be consumed by <= 2.0.9 |
| 3:22 PM |
pgier |
the things I want to do would be adding new tags, so I don't think it would break any compat with the old model |
| 3:22 PM |
pgier |
ah, I see what you mean |
| 3:23 PM |
Brian |
yeah i forget the details, i just remember there was an issue handling the different versions |
| 3:25 PM |
sebersole |
pgier: could you perhaps envision expressions? |
| 3:26 PM |
pgier |
sebersole: I'm not sure what you mean |
| 3:26 PM |
sebersole |
instead of allowing multiple properties, allow expressions |
| 3:26 PM |
sebersole |
for example |
| 3:26 PM |
pgier |
ah, yeah that is suggested in MNG-1753 |
| 3:27 PM |
sebersole |
ah |
| 3:27 PM |
sebersole |
ok |
| 3:27 PM |
pgier |
And I think it's a good idea |
| 3:27 PM |
sebersole |
what a coincidence |
| 3:27 PM |
sebersole |
:) |
| 3:27 PM |
brett |
:) |
| 3:28 PM |
pgier |
but it still would probably require changing the model |
| 3:28 PM |
brett |
handling versions to read the pom is pretty easy, even mixing them in a project. It's the repository that is hard. |
| 3:28 PM |
brett |
I still think we need an explicitly extensible format that focuses on the resolution and omits all the build stuff for the repository, instead of just the pom, but I've ranted enough on dev@ about that in the past |
| 3:28 PM |
brett |
with that, I should probably go to bed |
| 3:28 PM |
brett |
:) |
| 3:28 PM |
sebersole |
nite nite |
| 3:29 PM |
jason |
morgen |
| 3:30 PM |
sebersole |
pgier: btw, MNG-1753 is slightly different than what i meant |
| 3:30 PM |
sebersole |
i was thinking more along lines of JSP EL |
| 3:30 PM |
sebersole |
something that resolved to boolean |
| 3:32 PM |
pgier |
so it would be resolved right away in the pom? |
| 3:32 PM |
sebersole |
${some-prop} = 'some-value' OR ${steve} = 'insane' |
| 3:32 PM |
pgier |
I see what you mean |
| 3:33 PM |
pgier |
yeah, maybe some syntax within the tag to tell maven that this is a regex instead of having a different tag |
| 3:35 PM |
sebersole |
dont remember the details, but it seems there was a time I thought that would be useful |
| 3:42 PM |
jason |
not a chance |
| 3:43 PM |
jason |
has jelly shivers |
| 3:43 PM |
Brian |
the enforcer has a regex property rule |
| 3:43 PM |
Brian |
but you obviously can't activate a profile with it |
| 3:58 PM |
jimr |
Hi all |
| 3:59 PM |
jimr |
Is it possible to use the archetype plugin to build an archetype with a nested project structure? |
| 3:59 PM |
jimr |
(without creating multiple archetypes and just nesting them) |
| 4:00 PM |
wsmoak |
jimr: it wasn't with the old archetype plugin. I don't think we've seen what a "new" archetype looks like yet. |
| 4:00 PM |
jimr |
ah OK |
| 4:00 PM |
jimr |
"new" as in...? |
| 4:01 PM |
wsmoak |
trunk vs. the 1.0.x branch |
| 4:01 PM |
jimr |
ok, thanks |
| 4:01 PM |
wsmoak |
the bundles (the archetypes themselves) haven't been added back to trunk yet afaik |
| 4:02 PM |
jimr |
I don't suppose there's an ETA on that, is there? |
| 4:06 PM |
wsmoak |
you might try the create-from-project goal, and see what it does with a multi-module project |
| 4:06 PM |
jimr |
it complained a lot :) |
| 4:06 PM |
wsmoak |
ah. best bet is to ask on the user list and see if that motivates the developer to finish it :) |
| 4:07 PM |
jimr |
my parent project has no src directory (just a pom.xml) and create-from-project just said Source directory doesn't exists |
| 4:07 PM |
jimr |
ok :) |
| 4:07 PM |
jimr |
-> subscribe to the mailing list |
| 7:37 PM |
atpa8a |
hmm |
| 8:02 PM |
ben |
is there an easy way to convert groupId to a directory path? (com.blah.blah2 => com/blah/blah2) |
| 8:13 PM |
wsmoak |
ben: in what context? plugin development? shell scripting? |
| 8:13 PM |
ben |
archetype creation. |
| 8:14 PM |
ben |
want to drop some .properties into src/main/resources/groupId |
| 8:15 PM |
wsmoak |
is this relevant? http://jira.codehaus.org/browse/ARCHETYPE-65 |
| 8:15 PM |
wsmoak |
it used to work a long time ago if you just put them in src/main/resources, same as for classes -- it would "package" them. |
| 8:16 PM |
ben |
I thought it used to. |
| 8:16 PM |
ben |
yes, that's the exact problem. |
| 8:16 PM |
wsmoak |
but archetype has been rewritten, I'd hope the new one works right. what version of the archetype plugin are you using? |
| 8:16 PM |
ben |
unfortunately we're stuck on 1.0-alpha-7 due to http://jira.codehaus.org/browse/ARCHETYPE-89 :( |
| 8:18 PM |
wsmoak |
I'm losing track. I thought that was fixed in 2.0-alpha-3. |
| 8:19 PM |
wsmoak |
any chance you can test with the latest release just to see? |
| 8:19 PM |
ben |
our archetypes are still using the old 1.0 format. |
| 8:20 PM |
wsmoak |
that's fine, it understands them. (and there isn't a new 2.0 format yet afaik) |
| 8:20 PM |
ben |
http://maven.apache.org/plugins/maven-archetype-plugin/specification/archetype-metadata.html <-- for 2.0-alpha-3, looks completely different from 1.0 |
| 8:21 PM |
mkleint |
wsmoak: there is a new format, I'm using it exactly for this thing.. have resources in packages.. |
| 8:21 PM |
ben |
so we'll have to try 2.0 to see if it works. |
| 8:21 PM |
ben |
bugger. won't be able to do that for this release. |
| 8:22 PM |
ben |
thanks anyway, wendy :) |
| 8:24 PM |
wsmoak |
mkleint: is that a new format, or just a fixed bug? |
| 8:24 PM |
mkleint |
new format, it's placed in different file I think.. |
| 8:24 PM |
mkleint |
it also allows to define additional properties for entry |
| 8:25 PM |
wsmoak |
is it documented? I keep waiting for the new archtype bundles to appear on trunk, that's how I learned the format the last time :) |
| 8:26 PM |
ben |
the page I linked is all the doc I know about |
| 8:26 PM |
wsmoak |
I only see docs for the create-from-project goal. not for constructing one yourself. |
| 8:29 PM |
mkleint |
I don't trust the create from project goal. does it have a fileset style descriptor? |