You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Julien Stern <ju...@cryptolog.com> on 2008/10/10 12:46:33 UTC
Issue with netbeans and maven2
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
Baptiste MATHUS wrote:
> Hi,
> Well, to tackle the potential maven-netbeans integration problem, I guess
> you tested your project outside NB? What does it say? Which version of maven
> is it? Which maven-integration are you using?
> Did you specify the referenced maven xsd?
Baptiste,
thanks for your reply,
our project works fine outside NB. (Using Maven 2.0.7 or 2.0.8 or 2.0.9).
NetBeans IDE 6.1 (Build 200805300101)
Maven: 3.1.4
I believe we did reference the maven xsd. e.g. our pom.xml starts with:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
Actually, we can _build_ our project with NB (but I think it uses an
external maven, so that's normal), but the sources are not displayed,
which is kind of annoying :)
Milos Kleint suggested in an other reply that we test NB 6.5-dev and
maven-integration 4.0.x, which we will do...
Regards,
--
Julien
> CheerS.
>
> 2008/10/10 Julien Stern <ju...@cryptolog.com>
>
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Baptiste MATHUS <ml...@batmat.net>.
Hi,
Well, to tackle the potential maven-netbeans integration problem, I guess
you tested your project outside NB? What does it say? Which version of maven
is it? Which maven-integration are you using?
Did you specify the referenced maven xsd?
CheerS.
2008/10/10 Julien Stern <ju...@cryptolog.com>
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
RE: Issue with netbeans and maven2
Posted by Martin Gainty <mg...@hotmail.com>.
NV 5.5. does'nt support maven *..yet..*
which version of maven are you running?
?
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.
> Date: Mon, 13 Oct 2008 14:21:25 +0200
> From: julien.stern@cryptolog.com
> To: users@maven.apache.org
> Subject: Re: Issue with netbeans and maven2
>
> Milos,
>
> when trying to reproduce the issue with a basic project, I created a new
> user account and reinstalled _everything_ from scratch (netbeans,
> maven-integration, and also I did not start with any value in the
> "${HOME}/.netbeans*", nor any value in the "${HOME}/.m2/", and ... it
> worked...
>
> Considering I can still reproduce the issue by reinstalling everything
> (NB + maven-integration) but keeping old "${HOME}/.netbeans*" and old
> "${HOME}/.m2", I assume there is some kind of weird issue related to old
> settings or a bogus repo. I've looked around a bit, but unfortunately
> was unable to pinpoint the reason for failure.
>
> At any rate, it now works.
> Thank you very much for your kind support.
>
> Best regards,
>
> --
> Julien
>
> Milos Kleint wrote:
> > I assume your plugin is not in central repository. I recall there
> > is/was an issue with extensions beling looked for in wrong repository
> > (typically just repo1) instead of the declared ones. But that all
> > shall start working once you've built the project once, so I assume
> > it's not your case.
> > If you can reproduce on a sample project setup, please file it as bug,
> > I'll look into it. There must be something special about your setup as
> > I've been developing the maven support itself using nbm-maven-plugin
> > which defines artifact handler + lifecycle. I had the version declared
> > in the parent pom's pluginManagement section and used in child modules
> > (with additional configuration or without). Which sounds exactly like
> > what you have except that these projects can be opened without
> > problems.
> >
> > Milos
> >
> >
> > On Fri, Oct 10, 2008 at 6:01 PM, Julien Stern
> > <ju...@cryptolog.com> wrote:
> >> 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
> >>> <ju...@cryptolog.com> 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
> >>>>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
> >>>>>> For additional commands, e-mail: users-help@maven.apache.org
> >>>>>>
> >>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: users-help@maven.apache.org
> >>>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: users-help@maven.apache.org
> >>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
_________________________________________________________________
Get more out of the Web. Learn 10 hidden secrets of Windows Live.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
Milos Kleint wrote:
> hmmm.. too bad.
> I suppose it's either something with different local metadata in
> .m2/repository or the binaries for maven module were not exactly the
> same. (or both)
One last piece of info that might give you an hint (or not) :
- We currently have two boxes, one where it works, one where it does not.
- We cannot test sooo much the non-working one as, well... someone is
using it :)
- We did not manage to reproduce the issue on a fresh box (which is not
so bad, after all)
What we did on the dev box was:
1. trying to delete the plugin that caused the issue in the ~/.m2/repository
2. trying to manually rebuild the project
It still fails. We just do not understand what the difference can be.
Sorry we were unable to pinpoint the exact cause.
And thanks again.
--
Julien
> Milos
>
> On Mon, Oct 13, 2008 at 2:21 PM, Julien Stern
> <ju...@cryptolog.com> wrote:
>> Milos,
>>
>> when trying to reproduce the issue with a basic project, I created a new
>> user account and reinstalled _everything_ from scratch (netbeans,
>> maven-integration, and also I did not start with any value in the
>> "${HOME}/.netbeans*", nor any value in the "${HOME}/.m2/", and ... it
>> worked...
>>
>> Considering I can still reproduce the issue by reinstalling everything (NB +
>> maven-integration) but keeping old "${HOME}/.netbeans*" and old
>> "${HOME}/.m2", I assume there is some kind of weird issue related to old
>> settings or a bogus repo. I've looked around a bit, but unfortunately was
>> unable to pinpoint the reason for failure.
>>
>> At any rate, it now works.
>> Thank you very much for your kind support.
>>
>> Best regards,
>>
>> --
>> Julien
>>
>> Milos Kleint wrote:
>>> I assume your plugin is not in central repository. I recall there
>>> is/was an issue with extensions beling looked for in wrong repository
>>> (typically just repo1) instead of the declared ones. But that all
>>> shall start working once you've built the project once, so I assume
>>> it's not your case.
>>> If you can reproduce on a sample project setup, please file it as bug,
>>> I'll look into it. There must be something special about your setup as
>>> I've been developing the maven support itself using nbm-maven-plugin
>>> which defines artifact handler + lifecycle. I had the version declared
>>> in the parent pom's pluginManagement section and used in child modules
>>> (with additional configuration or without). Which sounds exactly like
>>> what you have except that these projects can be opened without
>>> problems.
>>>
>>> Milos
>>>
>>>
>>> On Fri, Oct 10, 2008 at 6:01 PM, Julien Stern
>>> <ju...@cryptolog.com> wrote:
>>>> 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
>>>>> <ju...@cryptolog.com> 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
>>>>>>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Activating proxy from command line
Posted by Johan Lindquist <jo...@kawoo.co.uk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have looked around but fail to find any docs on how to activate a
certain proxy (configured in my settings.xml) from the command line.
The docs for settings.xml hints that this could (should?) be possible.
Anyone used this or know if it is possible?
Cheers,
Johan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI94xUpHYnED7evioRAn4pAJsGLm77coNQVE4GuZBMRFLLhK7emACggXVi
8VvdOEUbQ+lp6EB1xxr/vGo=
=N73/
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Milos Kleint <mk...@gmail.com>.
hmmm.. too bad.
I suppose it's either something with different local metadata in
.m2/repository or the binaries for maven module were not exactly the
same. (or both)
Milos
On Mon, Oct 13, 2008 at 2:21 PM, Julien Stern
<ju...@cryptolog.com> wrote:
> Milos,
>
> when trying to reproduce the issue with a basic project, I created a new
> user account and reinstalled _everything_ from scratch (netbeans,
> maven-integration, and also I did not start with any value in the
> "${HOME}/.netbeans*", nor any value in the "${HOME}/.m2/", and ... it
> worked...
>
> Considering I can still reproduce the issue by reinstalling everything (NB +
> maven-integration) but keeping old "${HOME}/.netbeans*" and old
> "${HOME}/.m2", I assume there is some kind of weird issue related to old
> settings or a bogus repo. I've looked around a bit, but unfortunately was
> unable to pinpoint the reason for failure.
>
> At any rate, it now works.
> Thank you very much for your kind support.
>
> Best regards,
>
> --
> Julien
>
> Milos Kleint wrote:
>>
>> I assume your plugin is not in central repository. I recall there
>> is/was an issue with extensions beling looked for in wrong repository
>> (typically just repo1) instead of the declared ones. But that all
>> shall start working once you've built the project once, so I assume
>> it's not your case.
>> If you can reproduce on a sample project setup, please file it as bug,
>> I'll look into it. There must be something special about your setup as
>> I've been developing the maven support itself using nbm-maven-plugin
>> which defines artifact handler + lifecycle. I had the version declared
>> in the parent pom's pluginManagement section and used in child modules
>> (with additional configuration or without). Which sounds exactly like
>> what you have except that these projects can be opened without
>> problems.
>>
>> Milos
>>
>>
>> On Fri, Oct 10, 2008 at 6:01 PM, Julien Stern
>> <ju...@cryptolog.com> wrote:
>>>
>>> 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
>>>> <ju...@cryptolog.com> 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
>>>>>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
Milos,
when trying to reproduce the issue with a basic project, I created a new
user account and reinstalled _everything_ from scratch (netbeans,
maven-integration, and also I did not start with any value in the
"${HOME}/.netbeans*", nor any value in the "${HOME}/.m2/", and ... it
worked...
Considering I can still reproduce the issue by reinstalling everything
(NB + maven-integration) but keeping old "${HOME}/.netbeans*" and old
"${HOME}/.m2", I assume there is some kind of weird issue related to old
settings or a bogus repo. I've looked around a bit, but unfortunately
was unable to pinpoint the reason for failure.
At any rate, it now works.
Thank you very much for your kind support.
Best regards,
--
Julien
Milos Kleint wrote:
> I assume your plugin is not in central repository. I recall there
> is/was an issue with extensions beling looked for in wrong repository
> (typically just repo1) instead of the declared ones. But that all
> shall start working once you've built the project once, so I assume
> it's not your case.
> If you can reproduce on a sample project setup, please file it as bug,
> I'll look into it. There must be something special about your setup as
> I've been developing the maven support itself using nbm-maven-plugin
> which defines artifact handler + lifecycle. I had the version declared
> in the parent pom's pluginManagement section and used in child modules
> (with additional configuration or without). Which sounds exactly like
> what you have except that these projects can be opened without
> problems.
>
> Milos
>
>
> On Fri, Oct 10, 2008 at 6:01 PM, Julien Stern
> <ju...@cryptolog.com> wrote:
>> 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
>>> <ju...@cryptolog.com> 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
>>>>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Milos Kleint <mk...@gmail.com>.
I assume your plugin is not in central repository. I recall there
is/was an issue with extensions beling looked for in wrong repository
(typically just repo1) instead of the declared ones. But that all
shall start working once you've built the project once, so I assume
it's not your case.
If you can reproduce on a sample project setup, please file it as bug,
I'll look into it. There must be something special about your setup as
I've been developing the maven support itself using nbm-maven-plugin
which defines artifact handler + lifecycle. I had the version declared
in the parent pom's pluginManagement section and used in child modules
(with additional configuration or without). Which sounds exactly like
what you have except that these projects can be opened without
problems.
Milos
On Fri, Oct 10, 2008 at 6:01 PM, Julien Stern
<ju...@cryptolog.com> wrote:
> 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
>> <ju...@cryptolog.com> 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
>>>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
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
> <ju...@cryptolog.com> 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
>>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Milos Kleint <mk...@gmail.com>.
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
<ju...@cryptolog.com> 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
>> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
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
> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
Baptiste MATHUS wrote:
> 2008/10/10 Julien Stern <ju...@cryptolog.com>
>
>> Milos Kleint wrote:
>>
>>> what version of maven support in netbeans you have?
>>>
>> Milos,
>>
>> NetBeans IDE 6.1 (Build 200805300101)
>> Maven: 3.1.4
>
>
> Well, from what I know, this version of maven does not exist. Maven 3.x is
> still in active development state. So, I guess you're unlikely using this
> one.
> You're more likely using some maven 2.x version.
Sorry, I meant maven-integration: 3.1.4
We are indeed using 2.0.6, 2.0.7, 2.0.8 and 2.0.9 depending on the projects.
Cheers,
--
Julien
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Baptiste MATHUS <ml...@batmat.net>.
2008/10/10 Julien Stern <ju...@cryptolog.com>
> Milos Kleint wrote:
>
>> what version of maven support in netbeans you have?
>>
>
> Milos,
>
> NetBeans IDE 6.1 (Build 200805300101)
> Maven: 3.1.4
Well, from what I know, this version of maven does not exist. Maven 3.x is
still in active development state. So, I guess you're unlikely using this
one.
You're more likely using some maven 2.x version.
Cheers
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: Issue with netbeans and maven2
Posted by Julien Stern <ju...@cryptolog.com>.
Milos Kleint wrote:
> what version of maven support in netbeans you have?
Milos,
NetBeans IDE 6.1 (Build 200805300101)
Maven: 3.1.4
> 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.
This issue indeed seems to be similar to 135043 (well the issue
apparently tackles two problems: the RELEASE and the
<extensions>true</extensions> problems).
We will try the 6.5 development builds when we have time and let you
know if the issue still exists.
Thanks for your reply,
Regards,
--
Julien
> Regards
>
> Milos
>
>
> On Fri, Oct 10, 2008 at 12:46 PM, Julien Stern
> <ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Issue with netbeans and maven2
Posted by Milos Kleint <mk...@gmail.com>.
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
<ju...@cryptolog.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org