I've added something that will validate the plugin descriptor while
loading under MNG-4091.
The error will be:
[INFO] Internal error in the plugin manager getting plugin
'com.caucho:resin-maven-plugin': Plugin 'com.caucho:resin-maven-plugin:
3.1.6' has an invalid descriptor:
1) Plugin's des
I'm working on an enhancement to the error handling so this won't
cause too much confusion.
Cheers,
Brett
On 17/03/2009, at 9:42 AM, Benjamin Bentmann wrote:
Chris Handy wrote:
I am having an issue where the inclusion of a plugin using maven
2.0.9 works
fine but in maven 2.1.0-RC3 it comp
Yeah, I got that, but will it be interpolated...
at present by using MXpp3 I can get the raw model.
project.getOriginalModel() gives a kind-of interpolated without property
evaluation
project.getModel() gives the final values.
For 3.x will there be a route to all three or are we losing the midd
On 16-Mar-09, at 12:47 PM, Stephen Connolly wrote:
I have code which does what I need, so if enforcer is doing similar
then I'm
happy
-Stephen
BTW, how does this change in 3.x?
When you ask for the model it won't be mutated.
2009/3/16 Jason van Zyl
Brian had to do this in the enforc
Chris Handy wrote:
I am having an issue where the inclusion of a plugin using maven 2.0.9 works
fine but in maven 2.1.0-RC3 it complains saying it can not find the plugin
descriptor. I also saw the same behavior in RC2. I opened up the jar and
see the plugin.xml file in META-INF/maven/plugin.x
Can you please re-run with -X, capture the console output to a file
(using the 'tee' utility if you're on *nix works well), and attach that
file to a new JIRA issue at:
http://jira.codehaus.org/browse/MNG
If you can attach the test project that displays the problem, that will
make the process
I am having an issue where the inclusion of a plugin using maven 2.0.9 works
fine but in maven 2.1.0-RC3 it complains saying it can not find the plugin
descriptor. I also saw the same behavior in RC2. I opened up the jar and
see the plugin.xml file in META-INF/maven/plugin.xml. Here is the sampl
Jochen Wiedmann pisze:
On Mon, Mar 16, 2009 at 5:51 PM, John Casey wrote:
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another look things with RC3, and if everything is clean I'll call a vote in
the next day or two.
http://tinyurl.com/maven-2-1-0-RC3
(https://r
On Mon, Mar 16, 2009 at 5:51 PM, John Casey wrote:
> It looks like the last known bugs are resolved for 2.1.0. So, let's take
> another look things with RC3, and if everything is clean I'll call a vote in
> the next day or two.
>
> http://tinyurl.com/maven-2-1-0-RC3
> (https://repository.apache.o
I have code which does what I need, so if enforcer is doing similar then I'm
happy
-Stephen
BTW, how does this change in 3.x?
2009/3/16 Jason van Zyl
> Brian had to do this in the enforcer so there is code for 2.x there.
>
> In 3.x the model original model hierarchy is not mutated and stored a
Brian had to do this in the enforcer so there is code for 2.x there.
In 3.x the model original model hierarchy is not mutated and stored
along with the project.
On 16-Mar-09, at 10:26 AM, Stephen Connolly wrote:
Hey!
So either my memory is wrong or i remember somebody saying it's a "bad
th
Yeah, all I'm trying to grab is...
__
and
___
I know I have to do a little digging to figure out the artifactId and the
groupId if they are defined by properties, but I need to know:
1. if there is a version specified
2. what the text specifying the version is (to see if it uses ${_
Unless someone else knows more about it than I do, I'd say you're
probably right; it's in that 1%. :-)
The problem with skipping the project builder is that assembly of
project instances is really complex, and skipping any of these steps may
result in project instances with apparent bugs that
Hey!
So either my memory is wrong or i remember somebody saying it's a "bad
thing"(TM) to use MavenXpp3Reader from a plugin
I know that 99% of the time one should use model builder directly, but I
have a use case where I just want the results before *any* interpolation
what so ever is perform
Sorry the URL for the signup is:
https://docs.sonatype.org/display/COMM/Maven+Meetup+on+March+19th+and+20th+at+Sonatype
On 16-Mar-09, at 10:02 AM, Jason van Zyl wrote:
Hi,
Just a note that if you're interested in coming out please let us
know because we're on the threshold of needing to fin
Hi,
Just a note that if you're interested in coming out please let us know
because we're on the threshold of needing to find another venue as I
didn't expect 30 people to sign up on such short notice. If we get
more people who want to come out and we know by the end of the day we
can sort
Okay,
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another look things with RC3, and if everything is clean I'll call a
vote in the next day or two.
http://tinyurl.com/maven-2-1-0-RC3
(https://repository.apache.org/content/repositories/maven-staging-5078cd01de9bd9/
Hi,
We solved 12 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=Html&version=12616
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11150&status=1
Staging repo:
https://repository.apache.org/co
On Mon, Mar 16, 2009 at 10:59 AM, djeanprost wrote:
>
> Well,
>
> I have problem to use the last SNAPSHOT because of artifacts download
> problem and I don't have time to solve it.
ok, let me known if some artefacts aren't deployed.
>
> Anyway, I made this test using eclipse 3.3.0 :
> replace
Well,
I have problem to use the last SNAPSHOT because of artifacts download
problem and I don't have time to solve it.
Anyway, I made this test using eclipse 3.3.0 :
replaced every M2_REPO entries in my .classpath to /M2_REPO : didn't notice
anything wrong : it seems to work (when displaying java
20 matches
Mail list logo
