Milos,
we use ONLY explicits versions in ALL poms. We want reproducible builds
at all times ;) We do use dependencyManagement and pluginManagement a
lot though.
Specifically, the simplest project that fails is like this:
- We have the top-level pom and the actual project pom.
- The plugin that causes the problem in the project pom has one
configuration section and the <extensions>true</extensions> that
triggers the issue (see previous mail below).
- The parent pom only defines the version of this plugin in its
pluginManagement section
Note that the plugin defines a new type of artifact (with a new
ArtifactHandler) and a new LifecycleMapping (this is why we need
extensions to be true actually).
--
Julien
Milos Kleint wrote:
do you explicitly declare a version or you stick with RELEASE, LATEST
or not defined?
The workaround mentioned in the issues suggests to put explicit versions there.
If your's is different, it's probably not a duplicate but something
related only.
It might also be important where the plugin is defined..
is it in the project's pom, it's parent, it's parent parent? is it
defined in pluginManagement section in one of the parents?
Milos
On Fri, Oct 10, 2008 at 5:09 PM, Julien Stern
<[EMAIL PROTECTED]> wrote:
Milos,
oh well, we just tested with the daily NB snapshot and maven-integration
4.0.5. We still have the same issue.
The crux of the issue is really the <extensions>true</extensions> within a
plugin configuration e.g.:
<build>
<plugins>
<plugin>
<groupId>our.group.id</groupId>
<artifactId>our.artifact.id</artifactId>
<configuration>
our config here...
</configuration>
<extensions>true</extensions>
</plugin>
</plugins>
</build>
- if we _remove_ the line <extensions>true</extensions>, it's fine
- if we put <extensions>false</extensions>, it's fine
So, it is not a "syntax" error, but really a error condition triggered when
the value of extensions is set to true.
Regards,
--
Julien
Milos Kleint wrote:
what version of maven support in netbeans you have?
I suggest you try the 6.5 development builds (we're close to RC1, so
the stability is pretty good), and instal the 4.0.x version of maven
support from the update center. I recall I've done some fixes in this
area, but still usecases still fails. Primarily an issue with the
maven embedder being used in netbeans.
http://www.netbeans.org/issues/show_bug.cgi?id=135043
could be relevant.
http://www.netbeans.org/issues/show_bug.cgi?id=143185
If you issue is different, please file it in netbeans.org issuezilla,
preferably with a sample project or at least the relevant plugin
configuration.
Regards
Milos
On Fri, Oct 10, 2008 at 12:46 PM, Julien Stern
<[EMAIL PROTECTED]> wrote:
Hi list,
I hope this is the right place to query about this issue.
We have a Maven2 project that is displayed as <Badly formed maven
project>
(unknown).
After a (lot) of trial and errors, we manage to locate the source of the
problem. We have one plugin (homemade) that uses
<extensions>true</extensions>.
If we comment this line, netbeans is happy (but we cannot compile any
more).
If we keep this line, we have the above error.
Would anyone have an idea on what the issue could be?
(And how to solve it?)
Regards,
--
Julien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
