n should digest that and search the project artifacts
> for the relevant artifact (which it will need to do anyway, thus giving
> a "real" artifact object).
>
> - Brett
>
> Kris Bravo wrote:
>
>>I'd like to be able to refer to a dependency defined in a pom with
rivate Artifact schemaJar
Kris Bravo
Corridor Software, Inc.
http://www.corridor-software.us
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm happy to hear that! Thanks for the testing Dan.
--
Kris Bravo
Corridor Software, Inc.
http://www.corridor-software.us
> [ http://jira.codehaus.org/browse/MNG-643?page=comments#action_45044 ]
>
> Dan Tran commented on MNG-643:
> --
>
>
Can I take a look at your pom as well? Interested in knowing more about
what you are doing and how the include/exclude change affects it.
Kris
On Mon, 2005-08-22 at 16:12 -0500, Dan Tran (JIRA) wrote:
> [ http://jira.codehaus.org/browse/MNG-643?page=comments#action_44971 ]
>
> Dan Tran comm
I'm slow on the draw on the integration tests. Still getting acquainted
with how to do these in the manner trygve explained earlier. Sorry I
didn't get to it before you needed them.
Kris
On Mon, 2005-08-22 at 16:08 -0500, John Casey (JIRA) wrote:
> [ http://jira.codehaus.org/browse/MNG-643?p
You need to put the configuration in the plugin element. I suggest using
> and then the respective excludes instead.
>
> BTW, id is something unique so that if you need to add goals/config to
> it in a subproject or profile, you can select it
>
> - Brett
>
> Kris Brav
'org.apache.maven.plugins:maven-compiler-plugin' must be in an
executions element
Kris
On Tue, 2005-07-26 at 14:12 -0500, Kris Bravo wrote:
> I'm working on a patch to expose the inclusion and exclusion support of
> the plexus compiler in the compiler plugin.
>
> http://jira.
I'm working on a patch to expose the inclusion and exclusion support of
the plexus compiler in the compiler plugin.
http://jira.codehaus.org/browse/MNG-643
I'm confused about how to define the two configurations for two
different goals in the plugin description.
Assuming that filters could be set for the compile and testCompile goals,
passing them as parameters to the mojo would work just fine. I'll update
the ticket and add a patch later today.
Thanks btw. This one is very important to me, as much so as the xml beans
plugin was.
Kris
> [ http://j
I prefer 4) with the logged warnings. With 2) you potentially create more
significant runtime problems.
If, however, you decide to go with 2), a file included in an obvious
location (i.e., WEB-INF/lib/runtime.txt) listing the dropped dependencies
would help with the troubleshooting sessions.
Kri
yes it did:
http://jira.codehaus.org/browse/MNG-565
was the ticket and patch.
--
Kris Bravo
Corridor Software, Inc.
http://www.corridor-software.us
> [ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42735 ]
>
> John Casey commented o
"source/maven/trunk/maven-plugins/maven-xmlbeans-plugin/src/main/java/org/apache/maven/exception/CodedException.java"
"open source" is a directory but it's being split. m2 shows the javadoc
command ending with @files before executing it, and I'm wondering it the
file
> You didn't get my point.
>
> My point was that it is irrelevant if POMs in the repository are minimal or
> not.
> But it is extremely important that information which is the main maven
> repository is _not changing_!!!
>
I did get your overall point. But contrary to what you're now saying,
yo
What about taking a play from the Gentoo Portage book? Something similar
to the package masking ~arch keyword might do the trick:
Add an extra tag to the POM schema which indicates whether or not the
POM is stable.
Add a tag in the settings file which indicates whether or not you want
to use unst
There is nothing wrong with having or using the minimal POMs that can be
found in the repository. As a user if I find, for example, a sun library
for which no POM exists, I am willing to submit a basic POM which will
cause my build to continue unimpeded by its absence. I won't however,
stop every t
*checks pockets*
Not yet. Finishing up the xmlbeans plugin right now. But I'll add one to
the ticket later today.
In the mean time, what should I look for to determine if the
@requiresDependencyResolution tag is present? I want to be certain the
exception is only thrown if it isn't set and not whe
Westerhof wrote:
> On Fri, 8 Jul 2005, Kris Bravo wrote:
>
> You should define
>
> @requiresDependencyResolution compile
>
> in the class-level javadoc.
>
> > I have the following handle to the MavenProject defined in a plugin
> > written for maven 2.
> >
I have the following handle to the MavenProject defined in a plugin
written for maven 2.
/**
* The project whose project files to create.
*
* @parameter expression="${project}"
* @required
*/
private MavenProject project;
When I attempt to get the list of classpath eleme
/maven2/plugins/org/apache/maven/plugins/
maven-xmlbeans-plugin/maven-xmlbeans-plugin-RELEASE.version.txt
2.0-alpha-4-SNAPSHOT is the version of the xmlbean plugin.
I'm not sure I follow the reason it went for a version.txt file. Any ideas
how to get through/avoid this?
Thanks,
Kris Bravo
Cor
19 matches
Mail list logo
