subject:"Debugging Maven"

Re: debugging maven-deploy-plugin:deploy-file

2016-02-10 Thread Mehul Sanghvi

I was able to manually upload using the following command-line:

 mvn deploy:deploy-file -B -V -s
/path/to/build/dir/maven/settings-unix-buildmachine.xml
 -DrepositoryId=SNAPSHOTS-REPO-ID -Durl=
http://internal.nexus.host.com/nexus/content/repositories/snapshots-repo-being-used
-DgeneratePom=true -DgroupId=COM.GROUP.ID -Dversion=1.2.3.4.5-SNAPSHOT
-DartifactId=ARTIFACT-ID -Dfile=ZIP-FILE.zip -Dpackaging=zip
-Dclassifier=linux


Using mvn-3.0.5  it took just under 19 minutes to upload the zip file.
Using mvn-3.3.3 it took 22 seconds.


So there must be something wrong with the POM file that we are using.  I
will try and narrow it down and see what I can find.



On Tue, Feb 9, 2016 at 5:44 PM, Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> Yeah I can confirm, that I too couldn't find any reference to invalid
> login attempts in my Artifactory logs.
>
> Chris
>
> 
> Von: Mehul Sanghvi <mehul.sang...@gmail.com>
> Gesendet: Dienstag, 9. Februar 2016 21:49
> An: Maven Users List
> Betreff: Re: debugging maven-deploy-plugin:deploy-file
>
> What should I be looking at on the server side ?  I have access to it, with
> admin privs.
>
> I don't know much about it, and am the admin because the people that set it
> up have all left
> the company.  I'm "it" by default :)
>
> I looked at nexus.log, but nothing happens when I actually run maven with
> the pom.xml.  I have compared
> the help:effective-settings output for the jars-upload vs zip-upload
> profile, and the only difference was
> the profile name.
>
> I am trying to figure out from the server side if there is anything
> configured incorrectly somewhere, or some role/privilege
> that is incorrect, though that doesn't make sense, as its the same user
> writing tot he same repository in both cases.
>
>
>
>
> On Tue, Feb 9, 2016 at 10:40 AM, Christofer Dutz <
> christofer.d...@c-ware.de>
> wrote:
>
> > In my case I'm the only user and admin of the Repo Manager.
> >
> > And I know that I didn't update anything or even log-in to the front end
> > for months now. Also I didn't change anything with my settings.xml (even
> if
> > I thought I had but it turned out that it was in another settings.xml).
> > It's still the same as in one really old backup.
> >
> > I'll hope to find some time to investigate this as I know it will bite me
> > pretty soon.
> >
> > Chris
> >
> > ____
> > Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag
> von
> > Anders Hammar <and...@hammar.net>
> > Gesendet: Dienstag, 9. Februar 2016 16:27
> > An: Maven Users List
> > Betreff: Re: debugging maven-deploy-plugin:deploy-file
> >
> > Please keep in mind that there could be authorization rules in the
> > repository manager that gives access to some groupIds but not others, for
> > example. You should contact the ones responsible for your repo manager
> > instance and have them help you!
> >
> > /Anders
> >
> > On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <
> christofer.d...@c-ware.de
> > >
> > wrote:
> >
> > > Just to add my 50ct ... I too encountered a similar problem a few days
> > ago
> > > and am still having it.
> > >
> > > While I had a settings.xml that worked fine for ages I got the exact
> same
> > > Unauthorized errors.
> > > At first I thought I had a problem in my settings but I couldn't find
> > one.
> > > I "resolved" the problem, by disabling the settings.xml and pulling
> from
> > > maven central instead of my private repo ... but that's not a real
> > > resolution.
> > >
> > > I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it
> > > breaks most of my important plugins)
> > > My repo is an Artifactory (Haven't updated that for quite some time)
> > >
> > > As I don't seem to be alone with this eventually I'll use Wireshark
> > > investigate what's going over the wire. Mabe this will help find out
> > what's
> > > going wrong.
> > >
> > > Chris
> > >
> > > 
> > > Von: Mehul Sanghvi <mehul.sang...@gmail.com>
> > > Gesendet: Dienstag, 9. Februar 2016 15:02
> > > An: Maven Users List
> > > Cc: i...@soebes.de
> > > Betreff: Re: debugging maven-deploy-plugin:deploy-file
> > >
> > > The repositoryId is the same for both.  They are getting uploaded to
> the
> > > same repository.
> >

Re: debugging maven-deploy-plugin:deploy-file

2016-02-10 Thread Mehul Sanghvi

I was able to resolve it, after doing a more thorough comparison of the
help:effective-settings output. I had to clean out
all the noise in the output first.  After that I used Emacs and Ediff to do
the diff between the two log outputs I had.  That's when the following was
noticed:

Working POM:distributionManagement/repository/id = blah-blah-snapshotS

Failing POM:  distributionManagement/repository/id = blah-blah-snapshot


It helped to look at it in different colours with Emacs/ediff.

On a slightly different note, is there a way to get help:effective-settings
to only output the effective pom to a log file, rather than using shell
re-direct or tee  which will capture all the noise as well ?


cheers,

  mehul


On Wed, Feb 10, 2016 at 12:11 PM, Mehul Sanghvi <mehul.sang...@gmail.com>
wrote:

> I was able to manually upload using the following command-line:
>
>  mvn deploy:deploy-file -B -V -s
> /path/to/build/dir/maven/settings-unix-buildmachine.xml
>  -DrepositoryId=SNAPSHOTS-REPO-ID -Durl=
> http://internal.nexus.host.com/nexus/content/repositories/snapshots-repo-being-used
> -DgeneratePom=true -DgroupId=COM.GROUP.ID -Dversion=1.2.3.4.5-SNAPSHOT
> -DartifactId=ARTIFACT-ID -Dfile=ZIP-FILE.zip -Dpackaging=zip
> -Dclassifier=linux
>
>
> Using mvn-3.0.5  it took just under 19 minutes to upload the zip file.
> Using mvn-3.3.3 it took 22 seconds.
>
>
> So there must be something wrong with the POM file that we are using.  I
> will try and narrow it down and see what I can find.
>
>
>
> On Tue, Feb 9, 2016 at 5:44 PM, Christofer Dutz <christofer.d...@c-ware.de
> > wrote:
>
>> Yeah I can confirm, that I too couldn't find any reference to invalid
>> login attempts in my Artifactory logs.
>>
>> Chris
>>
>> 
>> Von: Mehul Sanghvi <mehul.sang...@gmail.com>
>> Gesendet: Dienstag, 9. Februar 2016 21:49
>> An: Maven Users List
>> Betreff: Re: debugging maven-deploy-plugin:deploy-file
>>
>> What should I be looking at on the server side ?  I have access to it,
>> with
>> admin privs.
>>
>> I don't know much about it, and am the admin because the people that set
>> it
>> up have all left
>> the company.  I'm "it" by default :)
>>
>> I looked at nexus.log, but nothing happens when I actually run maven with
>> the pom.xml.  I have compared
>> the help:effective-settings output for the jars-upload vs zip-upload
>> profile, and the only difference was
>> the profile name.
>>
>> I am trying to figure out from the server side if there is anything
>> configured incorrectly somewhere, or some role/privilege
>> that is incorrect, though that doesn't make sense, as its the same user
>> writing tot he same repository in both cases.
>>
>>
>>
>>
>> On Tue, Feb 9, 2016 at 10:40 AM, Christofer Dutz <
>> christofer.d...@c-ware.de>
>> wrote:
>>
>> > In my case I'm the only user and admin of the Repo Manager.
>> >
>> > And I know that I didn't update anything or even log-in to the front end
>> > for months now. Also I didn't change anything with my settings.xml
>> (even if
>> > I thought I had but it turned out that it was in another settings.xml).
>> > It's still the same as in one really old backup.
>> >
>> > I'll hope to find some time to investigate this as I know it will bite
>> me
>> > pretty soon.
>> >
>> > Chris
>> >
>> > 
>> > Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag
>> von
>> > Anders Hammar <and...@hammar.net>
>> > Gesendet: Dienstag, 9. Februar 2016 16:27
>> > An: Maven Users List
>> > Betreff: Re: debugging maven-deploy-plugin:deploy-file
>> >
>> > Please keep in mind that there could be authorization rules in the
>> > repository manager that gives access to some groupIds but not others,
>> for
>> > example. You should contact the ones responsible for your repo manager
>> > instance and have them help you!
>> >
>> > /Anders
>> >
>> > On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <
>> christofer.d...@c-ware.de
>> > >
>> > wrote:
>> >
>> > > Just to add my 50ct ... I too encountered a similar problem a few days
>> > ago
>> > > and am still having it.
>> > >
>> > > While I had a settings.xml that worked fine for ages I got the exact
>> same
>> > > Unauthorized errors.
>> > > At firs

Re: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Adrien Rivard

Hi,


I'm guessing you have a mismatch between the repositories ids you have at
execution and the configured  in your settings.xml (where the
username/password are).
Probably the repository id for upload-zip stuff is different that the one
for upload-jars?



On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi 
wrote:

>
>
> I have attached a copy of the pom.xml that I am using.
>
>
>
> On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise 
> wrote:
>
>> Hi,
>>
>> On 2/8/16 6:43 AM, Mehul Sanghvi wrote:
>>
>>> I have a project with multiple modules and sub-modules.   Two of the
>>> modules, use
>>> the same maven-deploy-plugin:deploy-file logic, just the artefacts they
>>> are
>>> working
>>>
>>
>>
>> Can you show an example of your deploy-file logic? Cause if you are
>> really using deploy-file goal within your pom file and in your life cycle
>> there is something wrong...
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> with are different.  One module uploads designated JARs to Nexus.  The
>>> other is
>>> meant for uploading ZIP files.  Both are activated only if their
>>> respective
>>> profiles
>>> are activated, -Pupload-jars and -Pupload-zips respectively.  Both
>>> modules
>>> share the same settings.xml information regarding repositories and
>>> servers.
>>>
>>>
>>> Upload-jars is able to successfully upload the JARs using deploy-file.
>>> Upload-zips always fails with:
>>>
>>>  Return code is: 401, ReasonPhrase:Unauthorized
>>>
>>> How do I figure out the credentials that are being used ?  When I use
>>>
>>>  mvn -X
>>>
>>> I do not see anything that would indicate what user/passwd combination is
>>> being used.   Any thoughts or suggestions ?
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
>
> --
> Mehul N. Sanghvi
> email: mehul.sang...@gmail.com
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
Adrien Rivard

AW: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Christofer Dutz

Just to add my 50ct ... I too encountered a similar problem a few days ago and 
am still having it.

While I had a settings.xml that worked fine for ages I got the exact same 
Unauthorized errors. 
At first I thought I had a problem in my settings but I couldn't find one. I 
"resolved" the problem, by disabling the settings.xml and pulling from maven 
central instead of my private repo ... but that's not a real resolution.

I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it breaks 
most of my important plugins)
My repo is an Artifactory (Haven't updated that for quite some time)

As I don't seem to be alone with this eventually I'll use Wireshark investigate 
what's going over the wire. Mabe this will help find out what's going wrong.

Chris

Von: Mehul Sanghvi <mehul.sang...@gmail.com>
Gesendet: Dienstag, 9. Februar 2016 15:02
An: Maven Users List
Cc: i...@soebes.de
Betreff: Re: debugging maven-deploy-plugin:deploy-file

The repositoryId is the same for both.  They are getting uploaded to the
same repository.

So face I have tested the following:

1.  verified username/password by logging into the web ui

2.  verified that server id in settings.xml matches the distribution
repository id in the pom.xml

3.  verified correct settings.xml was being used.  I used

   mvn help:effective-settings

4.  verified the url is correct and the protocol being used is http and not
https

5.  using one of the latest versions of maven i.e. 3.3.3

On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard <adrien.riv...@gmail.com>
wrote:

> Hi,
>
>
> I'm guessing you have a mismatch between the repositories ids you have at
> execution and the configured  in your settings.xml (where the
> username/password are).
> Probably the repository id for upload-zip stuff is different that the one
> for upload-jars?
>
>
>
> On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi <mehul.sang...@gmail.com>
> wrote:
>
> >
> >
> > I have attached a copy of the pom.xml that I am using.
> >
> >
> >
> > On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise <khmarba...@gmx.de>
> > wrote:
> >
> >> Hi,
> >>
> >> On 2/8/16 6:43 AM, Mehul Sanghvi wrote:
> >>
> >>> I have a project with multiple modules and sub-modules.   Two of the
> >>> modules, use
> >>> the same maven-deploy-plugin:deploy-file logic, just the artefacts they
> >>> are
> >>> working
> >>>
> >>
> >>
> >> Can you show an example of your deploy-file logic? Cause if you are
> >> really using deploy-file goal within your pom file and in your life
> cycle
> >> there is something wrong...
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >> with are different.  One module uploads designated JARs to Nexus.  The
> >>> other is
> >>> meant for uploading ZIP files.  Both are activated only if their
> >>> respective
> >>> profiles
> >>> are activated, -Pupload-jars and -Pupload-zips respectively.  Both
> >>> modules
> >>> share the same settings.xml information regarding repositories and
> >>> servers.
> >>>
> >>>
> >>> Upload-jars is able to successfully upload the JARs using deploy-file.
> >>> Upload-zips always fails with:
> >>>
> >>>  Return code is: 401, ReasonPhrase:Unauthorized
> >>>
> >>> How do I figure out the credentials that are being used ?  When I use
> >>>
> >>>  mvn -X
> >>>
> >>> I do not see anything that would indicate what user/passwd combination
> is
> >>> being used.   Any thoughts or suggestions ?
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> >
> > --
> > Mehul N. Sanghvi
> > email: mehul.sang...@gmail.com
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>
>
> --
> Adrien Rivard
>

--
Mehul N. Sanghvi
email: mehul.sang...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Anders Hammar

Please keep in mind that there could be authorization rules in the
repository manager that gives access to some groupIds but not others, for
example. You should contact the ones responsible for your repo manager
instance and have them help you!

/Anders

On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> Just to add my 50ct ... I too encountered a similar problem a few days ago
> and am still having it.
>
> While I had a settings.xml that worked fine for ages I got the exact same
> Unauthorized errors.
> At first I thought I had a problem in my settings but I couldn't find one.
> I "resolved" the problem, by disabling the settings.xml and pulling from
> maven central instead of my private repo ... but that's not a real
> resolution.
>
> I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it
> breaks most of my important plugins)
> My repo is an Artifactory (Haven't updated that for quite some time)
>
> As I don't seem to be alone with this eventually I'll use Wireshark
> investigate what's going over the wire. Mabe this will help find out what's
> going wrong.
>
> Chris
>
> 
> Von: Mehul Sanghvi <mehul.sang...@gmail.com>
> Gesendet: Dienstag, 9. Februar 2016 15:02
> An: Maven Users List
> Cc: i...@soebes.de
> Betreff: Re: debugging maven-deploy-plugin:deploy-file
>
> The repositoryId is the same for both.  They are getting uploaded to the
> same repository.
>
> So face I have tested the following:
>
> 1.  verified username/password by logging into the web ui
>
> 2.  verified that server id in settings.xml matches the distribution
> repository id in the pom.xml
>
> 3.  verified correct settings.xml was being used.  I used
>
>mvn help:effective-settings
>
> 4.  verified the url is correct and the protocol being used is http and not
> https
>
> 5.  using one of the latest versions of maven i.e. 3.3.3
>
>
>
>
>
> On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard <adrien.riv...@gmail.com>
> wrote:
>
> > Hi,
> >
> >
> > I'm guessing you have a mismatch between the repositories ids you have at
> > execution and the configured  in your settings.xml (where the
> > username/password are).
> > Probably the repository id for upload-zip stuff is different that the one
> > for upload-jars?
> >
> >
> >
> > On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi <mehul.sang...@gmail.com>
> > wrote:
> >
> > >
> > >
> > > I have attached a copy of the pom.xml that I am using.
> > >
> > >
> > >
> > > On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise <khmarba...@gmx.de
> >
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> On 2/8/16 6:43 AM, Mehul Sanghvi wrote:
> > >>
> > >>> I have a project with multiple modules and sub-modules.   Two of the
> > >>> modules, use
> > >>> the same maven-deploy-plugin:deploy-file logic, just the artefacts
> they
> > >>> are
> > >>> working
> > >>>
> > >>
> > >>
> > >> Can you show an example of your deploy-file logic? Cause if you are
> > >> really using deploy-file goal within your pom file and in your life
> > cycle
> > >> there is something wrong...
> > >>
> > >> Kind regards
> > >> Karl Heinz Marbaise
> > >>
> > >> with are different.  One module uploads designated JARs to Nexus.  The
> > >>> other is
> > >>> meant for uploading ZIP files.  Both are activated only if their
> > >>> respective
> > >>> profiles
> > >>> are activated, -Pupload-jars and -Pupload-zips respectively.  Both
> > >>> modules
> > >>> share the same settings.xml information regarding repositories and
> > >>> servers.
> > >>>
> > >>>
> > >>> Upload-jars is able to successfully upload the JARs using
> deploy-file.
> > >>> Upload-zips always fails with:
> > >>>
> > >>>  Return code is: 401, ReasonPhrase:Unauthorized
> > >>>
> > >>> How do I figure out the credentials that are being used ?  When I use
> > >>>
> > >>>  mvn -X
> > >>>
> > >>> I do not see anything that would indicate what user/passwd
> combination
> > is
> > >>> being used.   Any thoughts or suggestions ?
> > >>>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: users-h...@maven.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Mehul N. Sanghvi
> > > email: mehul.sang...@gmail.com
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> >
> >
> >
> > --
> > Adrien Rivard
> >
>
>
>
> --
> Mehul N. Sanghvi
> email: mehul.sang...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Mehul Sanghvi

The repositoryId is the same for both.  They are getting uploaded to the
same repository.

So face I have tested the following:

1.  verified username/password by logging into the web ui

2.  verified that server id in settings.xml matches the distribution
repository id in the pom.xml

3.  verified correct settings.xml was being used.  I used

   mvn help:effective-settings

4.  verified the url is correct and the protocol being used is http and not
https

5.  using one of the latest versions of maven i.e. 3.3.3





On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard 
wrote:

> Hi,
>
>
> I'm guessing you have a mismatch between the repositories ids you have at
> execution and the configured  in your settings.xml (where the
> username/password are).
> Probably the repository id for upload-zip stuff is different that the one
> for upload-jars?
>
>
>
> On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi 
> wrote:
>
> >
> >
> > I have attached a copy of the pom.xml that I am using.
> >
> >
> >
> > On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise 
> > wrote:
> >
> >> Hi,
> >>
> >> On 2/8/16 6:43 AM, Mehul Sanghvi wrote:
> >>
> >>> I have a project with multiple modules and sub-modules.   Two of the
> >>> modules, use
> >>> the same maven-deploy-plugin:deploy-file logic, just the artefacts they
> >>> are
> >>> working
> >>>
> >>
> >>
> >> Can you show an example of your deploy-file logic? Cause if you are
> >> really using deploy-file goal within your pom file and in your life
> cycle
> >> there is something wrong...
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >> with are different.  One module uploads designated JARs to Nexus.  The
> >>> other is
> >>> meant for uploading ZIP files.  Both are activated only if their
> >>> respective
> >>> profiles
> >>> are activated, -Pupload-jars and -Pupload-zips respectively.  Both
> >>> modules
> >>> share the same settings.xml information regarding repositories and
> >>> servers.
> >>>
> >>>
> >>> Upload-jars is able to successfully upload the JARs using deploy-file.
> >>> Upload-zips always fails with:
> >>>
> >>>  Return code is: 401, ReasonPhrase:Unauthorized
> >>>
> >>> How do I figure out the credentials that are being used ?  When I use
> >>>
> >>>  mvn -X
> >>>
> >>> I do not see anything that would indicate what user/passwd combination
> is
> >>> being used.   Any thoughts or suggestions ?
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> >
> > --
> > Mehul N. Sanghvi
> > email: mehul.sang...@gmail.com
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>
>
> --
> Adrien Rivard
>



-- 
Mehul N. Sanghvi
email: mehul.sang...@gmail.com

AW: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Christofer Dutz

In my case I'm the only user and admin of the Repo Manager.

And I know that I didn't update anything or even log-in to the front end for 
months now. Also I didn't change anything with my settings.xml (even if I 
thought I had but it turned out that it was in another settings.xml). It's 
still the same as in one really old backup.

I'll hope to find some time to investigate this as I know it will bite me 
pretty soon.

Chris


Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag von 
Anders Hammar <and...@hammar.net>
Gesendet: Dienstag, 9. Februar 2016 16:27
An: Maven Users List
Betreff: Re: debugging maven-deploy-plugin:deploy-file

Please keep in mind that there could be authorization rules in the
repository manager that gives access to some groupIds but not others, for
example. You should contact the ones responsible for your repo manager
instance and have them help you!

/Anders

On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> Just to add my 50ct ... I too encountered a similar problem a few days ago
> and am still having it.
>
> While I had a settings.xml that worked fine for ages I got the exact same
> Unauthorized errors.
> At first I thought I had a problem in my settings but I couldn't find one.
> I "resolved" the problem, by disabling the settings.xml and pulling from
> maven central instead of my private repo ... but that's not a real
> resolution.
>
> I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it
> breaks most of my important plugins)
> My repo is an Artifactory (Haven't updated that for quite some time)
>
> As I don't seem to be alone with this eventually I'll use Wireshark
> investigate what's going over the wire. Mabe this will help find out what's
> going wrong.
>
> Chris
>
> 
> Von: Mehul Sanghvi <mehul.sang...@gmail.com>
> Gesendet: Dienstag, 9. Februar 2016 15:02
> An: Maven Users List
> Cc: i...@soebes.de
> Betreff: Re: debugging maven-deploy-plugin:deploy-file
>
> The repositoryId is the same for both.  They are getting uploaded to the
> same repository.
>
> So face I have tested the following:
>
> 1.  verified username/password by logging into the web ui
>
> 2.  verified that server id in settings.xml matches the distribution
> repository id in the pom.xml
>
> 3.  verified correct settings.xml was being used.  I used
>
>mvn help:effective-settings
>
> 4.  verified the url is correct and the protocol being used is http and not
> https
>
> 5.  using one of the latest versions of maven i.e. 3.3.3
>
>
>
>
>
> On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard <adrien.riv...@gmail.com>
> wrote:
>
> > Hi,
> >
> >
> > I'm guessing you have a mismatch between the repositories ids you have at
> > execution and the configured  in your settings.xml (where the
> > username/password are).
> > Probably the repository id for upload-zip stuff is different that the one
> > for upload-jars?
> >
> >
> >
> > On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi <mehul.sang...@gmail.com>
> > wrote:
> >
> > >
> > >
> > > I have attached a copy of the pom.xml that I am using.
> > >
> > >
> > >
> > > On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise <khmarba...@gmx.de
> >
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> On 2/8/16 6:43 AM, Mehul Sanghvi wrote:
> > >>
> > >>> I have a project with multiple modules and sub-modules.   Two of the
> > >>> modules, use
> > >>> the same maven-deploy-plugin:deploy-file logic, just the artefacts
> they
> > >>> are
> > >>> working
> > >>>
> > >>
> > >>
> > >> Can you show an example of your deploy-file logic? Cause if you are
> > >> really using deploy-file goal within your pom file and in your life
> > cycle
> > >> there is something wrong...
> > >>
> > >> Kind regards
> > >> Karl Heinz Marbaise
> > >>
> > >> with are different.  One module uploads designated JARs to Nexus.  The
> > >>> other is
> > >>> meant for uploading ZIP files.  Both are activated only if their
> > >>> respective
> > >>> profiles
> > >>> are activated, -Pupload-jars and -Pupload-zips respectively.  Both
> > >>> modules
> > >>> share the same settings.xml information regarding repositories and
> &

Re: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Mehul Sanghvi

What should I be looking at on the server side ?  I have access to it, with
admin privs.

I don't know much about it, and am the admin because the people that set it
up have all left
the company.  I'm "it" by default :)

I looked at nexus.log, but nothing happens when I actually run maven with
the pom.xml.  I have compared
the help:effective-settings output for the jars-upload vs zip-upload
profile, and the only difference was
the profile name.

I am trying to figure out from the server side if there is anything
configured incorrectly somewhere, or some role/privilege
that is incorrect, though that doesn't make sense, as its the same user
writing tot he same repository in both cases.




On Tue, Feb 9, 2016 at 10:40 AM, Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> In my case I'm the only user and admin of the Repo Manager.
>
> And I know that I didn't update anything or even log-in to the front end
> for months now. Also I didn't change anything with my settings.xml (even if
> I thought I had but it turned out that it was in another settings.xml).
> It's still the same as in one really old backup.
>
> I'll hope to find some time to investigate this as I know it will bite me
> pretty soon.
>
> Chris
>
> 
> Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag von
> Anders Hammar <and...@hammar.net>
> Gesendet: Dienstag, 9. Februar 2016 16:27
> An: Maven Users List
> Betreff: Re: debugging maven-deploy-plugin:deploy-file
>
> Please keep in mind that there could be authorization rules in the
> repository manager that gives access to some groupIds but not others, for
> example. You should contact the ones responsible for your repo manager
> instance and have them help you!
>
> /Anders
>
> On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <christofer.d...@c-ware.de
> >
> wrote:
>
> > Just to add my 50ct ... I too encountered a similar problem a few days
> ago
> > and am still having it.
> >
> > While I had a settings.xml that worked fine for ages I got the exact same
> > Unauthorized errors.
> > At first I thought I had a problem in my settings but I couldn't find
> one.
> > I "resolved" the problem, by disabling the settings.xml and pulling from
> > maven central instead of my private repo ... but that's not a real
> > resolution.
> >
> > I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it
> > breaks most of my important plugins)
> > My repo is an Artifactory (Haven't updated that for quite some time)
> >
> > As I don't seem to be alone with this eventually I'll use Wireshark
> > investigate what's going over the wire. Mabe this will help find out
> what's
> > going wrong.
> >
> > Chris
> >
> > 
> > Von: Mehul Sanghvi <mehul.sang...@gmail.com>
> > Gesendet: Dienstag, 9. Februar 2016 15:02
> > An: Maven Users List
> > Cc: i...@soebes.de
> > Betreff: Re: debugging maven-deploy-plugin:deploy-file
> >
> > The repositoryId is the same for both.  They are getting uploaded to the
> > same repository.
> >
> > So face I have tested the following:
> >
> > 1.  verified username/password by logging into the web ui
> >
> > 2.  verified that server id in settings.xml matches the distribution
> > repository id in the pom.xml
> >
> > 3.  verified correct settings.xml was being used.  I used
> >
> >mvn help:effective-settings
> >
> > 4.  verified the url is correct and the protocol being used is http and
> not
> > https
> >
> > 5.  using one of the latest versions of maven i.e. 3.3.3
> >
> >
> >
> >
> >
> > On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard <adrien.riv...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > >
> > > I'm guessing you have a mismatch between the repositories ids you have
> at
> > > execution and the configured  in your settings.xml (where
> the
> > > username/password are).
> > > Probably the repository id for upload-zip stuff is different that the
> one
> > > for upload-jars?
> > >
> > >
> > >
> > > On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi <mehul.sang...@gmail.com
> >
> > > wrote:
> > >
> > > >
> > > >
> > > > I have attached a copy of the pom.xml that I am using.
> > > >
> > > >
> > > >
> > > > On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise <
> khmarba...@g

AW: debugging maven-deploy-plugin:deploy-file

2016-02-09 Thread Christofer Dutz

Yeah I can confirm, that I too couldn't find any reference to invalid login 
attempts in my Artifactory logs.

Chris


Von: Mehul Sanghvi <mehul.sang...@gmail.com>
Gesendet: Dienstag, 9. Februar 2016 21:49
An: Maven Users List
Betreff: Re: debugging maven-deploy-plugin:deploy-file

What should I be looking at on the server side ?  I have access to it, with
admin privs.

I don't know much about it, and am the admin because the people that set it
up have all left
the company.  I'm "it" by default :)

I looked at nexus.log, but nothing happens when I actually run maven with
the pom.xml.  I have compared
the help:effective-settings output for the jars-upload vs zip-upload
profile, and the only difference was
the profile name.

I am trying to figure out from the server side if there is anything
configured incorrectly somewhere, or some role/privilege
that is incorrect, though that doesn't make sense, as its the same user
writing tot he same repository in both cases.




On Tue, Feb 9, 2016 at 10:40 AM, Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> In my case I'm the only user and admin of the Repo Manager.
>
> And I know that I didn't update anything or even log-in to the front end
> for months now. Also I didn't change anything with my settings.xml (even if
> I thought I had but it turned out that it was in another settings.xml).
> It's still the same as in one really old backup.
>
> I'll hope to find some time to investigate this as I know it will bite me
> pretty soon.
>
> Chris
>
> 
> Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag von
> Anders Hammar <and...@hammar.net>
> Gesendet: Dienstag, 9. Februar 2016 16:27
> An: Maven Users List
> Betreff: Re: debugging maven-deploy-plugin:deploy-file
>
> Please keep in mind that there could be authorization rules in the
> repository manager that gives access to some groupIds but not others, for
> example. You should contact the ones responsible for your repo manager
> instance and have them help you!
>
> /Anders
>
> On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <christofer.d...@c-ware.de
> >
> wrote:
>
> > Just to add my 50ct ... I too encountered a similar problem a few days
> ago
> > and am still having it.
> >
> > While I had a settings.xml that worked fine for ages I got the exact same
> > Unauthorized errors.
> > At first I thought I had a problem in my settings but I couldn't find
> one.
> > I "resolved" the problem, by disabling the settings.xml and pulling from
> > maven central instead of my private repo ... but that's not a real
> > resolution.
> >
> > I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it
> > breaks most of my important plugins)
> > My repo is an Artifactory (Haven't updated that for quite some time)
> >
> > As I don't seem to be alone with this eventually I'll use Wireshark
> > investigate what's going over the wire. Mabe this will help find out
> what's
> > going wrong.
> >
> > Chris
> >
> > 
> > Von: Mehul Sanghvi <mehul.sang...@gmail.com>
> > Gesendet: Dienstag, 9. Februar 2016 15:02
> > An: Maven Users List
> > Cc: i...@soebes.de
> > Betreff: Re: debugging maven-deploy-plugin:deploy-file
> >
> > The repositoryId is the same for both.  They are getting uploaded to the
> > same repository.
> >
> > So face I have tested the following:
> >
> > 1.  verified username/password by logging into the web ui
> >
> > 2.  verified that server id in settings.xml matches the distribution
> > repository id in the pom.xml
> >
> > 3.  verified correct settings.xml was being used.  I used
> >
> >mvn help:effective-settings
> >
> > 4.  verified the url is correct and the protocol being used is http and
> not
> > https
> >
> > 5.  using one of the latest versions of maven i.e. 3.3.3
> >
> >
> >
> >
> >
> > On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard <adrien.riv...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > >
> > > I'm guessing you have a mismatch between the repositories ids you have
> at
> > > execution and the configured  in your settings.xml (where
> the
> > > username/password are).
> > > Probably the repository id for upload-zip stuff is different that the
> one
> > > for upload-jars?
> > >
> > >
> > >
> > > On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi <mehul.sang

Re: debugging maven-deploy-plugin:deploy-file

2016-02-08 Thread Karl Heinz Marbaise


Hi,

On 2/8/16 6:43 AM, Mehul Sanghvi wrote:

I have a project with multiple modules and sub-modules.   Two of the
modules, use
the same maven-deploy-plugin:deploy-file logic, just the artefacts they are
working



Can you show an example of your deploy-file logic? Cause if you are 
really using deploy-file goal within your pom file and in your life 
cycle there is something wrong...


Kind regards
Karl Heinz Marbaise


with are different.  One module uploads designated JARs to Nexus.  The
other is
meant for uploading ZIP files.  Both are activated only if their respective
profiles
are activated, -Pupload-jars and -Pupload-zips respectively.  Both modules
share the same settings.xml information regarding repositories and servers.


Upload-jars is able to successfully upload the JARs using deploy-file.
Upload-zips always fails with:

 Return code is: 401, ReasonPhrase:Unauthorized

How do I figure out the credentials that are being used ?  When I use

 mvn -X

I do not see anything that would indicate what user/passwd combination is
being used.   Any thoughts or suggestions ?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: debugging maven-deploy-plugin:deploy-file

2016-02-08 Thread Adrien Rivard

Hi,

If it is effectively using the same configuration, the problem could be on
the nexus level (users / permission).
Try uploading it directly from the nexus GUI.

That said I don't recall anything that would prevent iploading zip and not
jars so your problem can still be on maven level.

Can you try without profiles for example ? (avoid profile if it possible).

Also Nexus logs can have useful informations if you have access to them.

On Mon, Feb 8, 2016 at 6:43 AM, Mehul Sanghvi 
wrote:

> I have a project with multiple modules and sub-modules.   Two of the
> modules, use
> the same maven-deploy-plugin:deploy-file logic, just the artefacts they are
> working
> with are different.  One module uploads designated JARs to Nexus.  The
> other is
> meant for uploading ZIP files.  Both are activated only if their respective
> profiles
> are activated, -Pupload-jars and -Pupload-zips respectively.  Both modules
> share the same settings.xml information regarding repositories and servers.
>
>
> Upload-jars is able to successfully upload the JARs using deploy-file.
> Upload-zips always fails with:
>
> Return code is: 401, ReasonPhrase:Unauthorized
>
> How do I figure out the credentials that are being used ?  When I use
>
> mvn -X
>
> I do not see anything that would indicate what user/passwd combination is
> being used.   Any thoughts or suggestions ?
>
>
> cheers,
>
>   mehul
>
> --
> Mehul N. Sanghvi
> email: mehul.sang...@gmail.com
>

-- 
Adrien Rivard

Re: debugging maven-deploy-plugin:deploy-file

2016-02-08 Thread Mehul Sanghvi

I have attached a copy of the pom.xml that I am using.



On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise 
wrote:

> Hi,
>
> On 2/8/16 6:43 AM, Mehul Sanghvi wrote:
>
>> I have a project with multiple modules and sub-modules.   Two of the
>> modules, use
>> the same maven-deploy-plugin:deploy-file logic, just the artefacts they
>> are
>> working
>>
>
>
> Can you show an example of your deploy-file logic? Cause if you are really
> using deploy-file goal within your pom file and in your life cycle there is
> something wrong...
>
> Kind regards
> Karl Heinz Marbaise
>
> with are different.  One module uploads designated JARs to Nexus.  The
>> other is
>> meant for uploading ZIP files.  Both are activated only if their
>> respective
>> profiles
>> are activated, -Pupload-jars and -Pupload-zips respectively.  Both modules
>> share the same settings.xml information regarding repositories and
>> servers.
>>
>>
>> Upload-jars is able to successfully upload the JARs using deploy-file.
>> Upload-zips always fails with:
>>
>>  Return code is: 401, ReasonPhrase:Unauthorized
>>
>> How do I figure out the credentials that are being used ?  When I use
>>
>>  mvn -X
>>
>> I do not see anything that would indicate what user/passwd combination is
>> being used.   Any thoughts or suggestions ?
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
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;>
	4.0.0
	GROUP.ID
	publish-zip-artifacts
	ZIP PUBLISH
	pom	
	
		ORG.GROUP.ID
		SOME-ARTIFACT-ID
		1.2.3-SNAPSHOT
	
	
		${project.distributionManagement.snapshotRepository.id}
		${project.distributionManagement.snapshotRepository.url}
		GROUP.ID
		
	
	
		
			PROFILE-ZIP-UPLOAD
			

	integration-releases
	Internal Release Repository
	http://nexus.internal.com:8081/nexus/content/repositories/repo-releases
	true


	integration-snapshot
	Internal Snapshot Repository
	http://internal.nexus.com:8081/nexus/content/repositories/repo-snapshot
	false

			
			

	
		org.apache.maven.plugins
		maven-deploy-plugin
		2.7
		
			
			
deploy-artifact-zip
install

	deploy-file


	${repositoryId}
	${url}
	${groupId}
	SOME-ARTIFACT
	${project.version}
	${project.parent.basedir}/path/to/target-${osArch}-${osName}.zip	
	
	
	${release.platform}
	true
	zip

			
			 			
		
	

			
		
	
	
		
			ORG.GROUP.ID
			SOME-ASSEMBLY
			${project.version}
			pom
		
	


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

debugging maven-deploy-plugin:deploy-file

2016-02-07 Thread Mehul Sanghvi

I have a project with multiple modules and sub-modules.   Two of the
modules, use
the same maven-deploy-plugin:deploy-file logic, just the artefacts they are
working
with are different.  One module uploads designated JARs to Nexus.  The
other is
meant for uploading ZIP files.  Both are activated only if their respective
profiles
are activated, -Pupload-jars and -Pupload-zips respectively.  Both modules
share the same settings.xml information regarding repositories and servers.


Upload-jars is able to successfully upload the JARs using deploy-file.
Upload-zips always fails with:

Return code is: 401, ReasonPhrase:Unauthorized

How do I figure out the credentials that are being used ?  When I use

mvn -X

I do not see anything that would indicate what user/passwd combination is
being used.   Any thoughts or suggestions ?


cheers,

  mehul

-- 
Mehul N. Sanghvi
email: mehul.sang...@gmail.com

Re: Have to reconnect each time while running debugging maven remotely?

2014-08-12 Thread Adrien Rivard

Hi,

I've never used it but it the debug remote java application launch
configuration there is an option to listen to jvm (connection type :
standard( socket listen) ) . Presumably the forked jvms will attached
themself to the debugger contrary to the usual case where the debugger is
attached to the jvm.

On Tue, Aug 12, 2014 at 2:35 AM, salilsurendran salilsurend...@gmail.com
wrote:

Hello,
Due to legacy reasons we have forkMode set to 'pertest' in our pom.
This
configuration can't be changed. However when I remote debug in eclipse(or
command line) I use `-Dmaven.surefire.debug=-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent
-Djava.compiler=NONE test -DforkMode=never`. I then connect to port 8000
from eclipse. However since forkMode is set to pertest each time a jvm is
spawned to run a test which means that I have to remote connect every time
to keep the test running and I have over 3000 tests. The -DforkMode=never
never takes effect and is overridden with what is the in the pom. Is this
the right behavior? What can I do to have the remote debugger reconnect
even
if the jvm forks?

--
View this message in context:
http://maven.40175.n5.nabble.com/Have-to-reconnect-each-time-while-running-debugging-maven-remotely-tp5802153.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

--
Adrien Rivard

Have to reconnect each time while running debugging maven remotely?

2014-08-11 Thread salilsurendran

Hello,
   Due to legacy reasons we have forkMode set to  'pertest' in our pom. This
configuration can't be changed. However when I remote debug in eclipse(or
command line) I use `-Dmaven.surefire.debug=-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent
-Djava.compiler=NONE test -DforkMode=never`. I then connect to port 8000
from eclipse. However since forkMode is set to pertest each time a jvm is
spawned to run a test which means that I have to remote connect every time
to keep the test running and I have over 3000 tests. The -DforkMode=never
never takes effect and is overridden with what is the in the pom. Is this
the right behavior? What can I do to have the remote debugger reconnect even
if the jvm forks?



--
View this message in context: 
http://maven.40175.n5.nabble.com/Have-to-reconnect-each-time-while-running-debugging-maven-remotely-tp5802153.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

best way to attach source for debugging maven plugin

2013-11-05 Thread Steve Cohen

I have a need to debug the maven-assembly-plugin which is not 
functioning correctly.  I have found the instructions for setting up a 
debugging environment for maven itself within eclipse.


What is the best way to get the source for this plugin so that it can be 
used by the debugging process.  I know I can download it from svn, and 
attach in Eclipse, but is there a maven command to do that?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: best way to attach source for debugging maven plugin

2013-11-05 Thread Olivier Lamy

Use mvnDebug cli instead of mvn

--
Olivier
On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote:

 I have a need to debug the maven-assembly-plugin which is not functioning
 correctly.  I have found the instructions for setting up a debugging
 environment for maven itself within eclipse.

 What is the best way to get the source for this plugin so that it can be
 used by the debugging process.  I know I can download it from svn, and
 attach in Eclipse, but is there a maven command to do that?

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: best way to attach source for debugging maven plugin

2013-11-05 Thread Steve Cohen


On 11/05/2013 04:22 PM, Olivier Lamy wrote:

Use mvnDebug cli instead of mvn

--
Olivier
On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote:


I have a need to debug the maven-assembly-plugin which is not functioning
correctly.  I have found the instructions for setting up a debugging
environment for maven itself within eclipse.

What is the best way to get the source for this plugin so that it can be
used by the debugging process.  I know I can download it from svn, and
attach in Eclipse, but is there a maven command to do that?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




Thanks, I am using the mvnDebug cli.  That does seems to bring in the 
Maven (core and plugin source) but it does not bring in the source for 
the Codehaus Plexus stuff called by the plugin, which I also need to see 
for this debugging.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: best way to attach source for debugging maven plugin

2013-11-05 Thread Russell Gold

Bringing in the source should be a function of your editor. What are you using? 
It works fine for me in IntelliJ

- Russ

On Nov 5, 2013, at 6:09 PM, Steve Cohen sco...@javactivity.org wrote:

 On 11/05/2013 04:22 PM, Olivier Lamy wrote:
 Use mvnDebug cli instead of mvn
 
 --
 Olivier
 On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote:
 
 I have a need to debug the maven-assembly-plugin which is not functioning
 correctly.  I have found the instructions for setting up a debugging
 environment for maven itself within eclipse.
 
 What is the best way to get the source for this plugin so that it can be
 used by the debugging process.  I know I can download it from svn, and
 attach in Eclipse, but is there a maven command to do that?
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 Thanks, I am using the mvnDebug cli.  That does seems to bring in the Maven 
 (core and plugin source) but it does not bring in the source for the Codehaus 
 Plexus stuff called by the plugin, which I also need to see for this 
 debugging.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 

-
Author, Getting Started with Apache Maven 
http://www.packtpub.com/getting-started-with-apache-maven/video

Come read my webnovel, Take a Lemon http://www.takealemon.com, 
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!

Re: best way to attach source for debugging maven plugin

2013-11-05 Thread Steve Cohen

I'm using Eclipse (with m2eclipse).  Basic problem there is that plugins 
are not normally dependencies of a maven project, therefore do not show 
up anywhere where I can apply the Maven-get source function.  I suppose 
I could make them dependencies but that seems wrong.



On 11/05/2013 05:51 PM, Russell Gold wrote:

Bringing in the source should be a function of your editor. What are you using? 
It works fine for me in IntelliJ

- Russ

On Nov 5, 2013, at 6:09 PM, Steve Cohen sco...@javactivity.org wrote:


On 11/05/2013 04:22 PM, Olivier Lamy wrote:

Use mvnDebug cli instead of mvn

--
Olivier
On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote:


I have a need to debug the maven-assembly-plugin which is not functioning
correctly.  I have found the instructions for setting up a debugging
environment for maven itself within eclipse.

What is the best way to get the source for this plugin so that it can be
used by the debugging process.  I know I can download it from svn, and
attach in Eclipse, but is there a maven command to do that?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





Thanks, I am using the mvnDebug cli.  That does seems to bring in the Maven 
(core and plugin source) but it does not bring in the source for the Codehaus 
Plexus stuff called by the plugin, which I also need to see for this debugging.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
Author, Getting Started with Apache Maven 
http://www.packtpub.com/getting-started-with-apache-maven/video

Come read my webnovel, Take a Lemon http://www.takealemon.com,
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!











-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: best way to attach source for debugging maven plugin

2013-11-05 Thread Baptiste Mathus

Hi,
I think you are just gonna have to retrieve the code manually inside your
ide.
Cheers
Le 6 nov. 2013 03:34, Steve Cohen sco...@javactivity.org a écrit :

 I'm using Eclipse (with m2eclipse).  Basic problem there is that plugins
 are not normally dependencies of a maven project, therefore do not show up
 anywhere where I can apply the Maven-get source function.  I suppose I
 could make them dependencies but that seems wrong.


 On 11/05/2013 05:51 PM, Russell Gold wrote:

 Bringing in the source should be a function of your editor. What are you
 using? It works fine for me in IntelliJ

 - Russ

 On Nov 5, 2013, at 6:09 PM, Steve Cohen sco...@javactivity.org wrote:

  On 11/05/2013 04:22 PM, Olivier Lamy wrote:

 Use mvnDebug cli instead of mvn

 --
 Olivier
 On Nov 6, 2013 8:09 AM, Steve Cohen sco...@javactivity.org wrote:

  I have a need to debug the maven-assembly-plugin which is not
 functioning
 correctly.  I have found the instructions for setting up a debugging
 environment for maven itself within eclipse.

 What is the best way to get the source for this plugin so that it can
 be
 used by the debugging process.  I know I can download it from svn, and
 attach in Eclipse, but is there a maven command to do that?

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



  Thanks, I am using the mvnDebug cli.  That does seems to bring in the
 Maven (core and plugin source) but it does not bring in the source for the
 Codehaus Plexus stuff called by the plugin, which I also need to see for
 this debugging.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 -
 Author, Getting Started with Apache Maven http://www.packtpub.com/
 getting-started-with-apache-maven/video

 Come read my webnovel, Take a Lemon http://www.takealemon.com,
 and listen to the Misfile radio play http://www.fuzzyfacetheater.
 com/misfile/!










 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: Debugging maven-dependency-plugin

2011-03-17 Thread Marc Rohlfs

If can't find useful information in the debug output, it's getting 
somewhat hard to analyse. In the last instance You could try to debug it 
using the IDE:
1. Download the sources of the dependency plugin version Your're using 
from the SVN and integrate/import it in Your IDE.
2. Set a debug break point at the begining of the execute() method in 
the CopyDependenciesMojo class.
3. Start Your build using the command 'mvnDebug' (instead of 'mvn'). 
Maven now waits for a remote debugger to connect until it starts the build.
4. In Your IDE, start the remote debugger for the 
maven-dependency-plugin project (using port 8000). The execution of the 
Maven build should stop at the break point and You can start debugging ...



BTW: I think I have an idea why the servlet-api-2.3.jar isn't excluded 
when copying the dependencies. Try using a dot instead of a dash:

excludeGroupIdsjavax.servlet/excludeGroupIds

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Debugging maven-dependency-plugin

2011-03-17 Thread Chris


On 3/17/2011 7:48 AM, Marc Rohlfs wrote:

If can't find useful information in the debug output, it's getting
somewhat hard to analyse. In the last instance You could try to debug it
using the IDE:
1. Download the sources of the dependency plugin version Your're using
from the SVN and integrate/import it in Your IDE.
2. Set a debug break point at the begining of the execute() method in
the CopyDependenciesMojo class.
3. Start Your build using the command 'mvnDebug' (instead of 'mvn').
Maven now waits for a remote debugger to connect until it starts the build.
4. In Your IDE, start the remote debugger for the
maven-dependency-plugin project (using port 8000). The execution of the
Maven build should stop at the break point and You can start debugging ...


BTW: I think I have an idea why the servlet-api-2.3.jar isn't excluded
when copying the dependencies. Try using a dot instead of a dash:
excludeGroupIdsjavax.servlet/excludeGroupIds


Excellent -- replacing the dash with a dot did it. Looks like I don't 
have to debug it at all. Though I'm hoping that other mystery jars 
aren't showing up as well...



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Debugging maven-dependency-plugin

2011-03-16 Thread Chris


I've having an odd problem with the maven dependency plugin.

I'm using it to copy all the jars upon which my app depends. It's 
copying one particular jar, servlet-api-2.3.jar, which it shouldn't.


How do I figure out *why* it's copying that jar?

I've already tried running mvn dependency:tree from the command line, 
and that particular jar does not show up in the output.


I've also tried to exclude it explicitly using excludeGroupIds:

execution
  phasepackage/phase
  goals
goalcopy-dependencies/goal
  /goals
  configuration
includeScopecompile/includeScope
excludeGroupIdsjavax-servlet/excludeGroupIds
outputDirectorytarget/lib/outputDirectory
  /configuration
/execution

But it still gets copied.

I also enabled debug output during the maven build, but the dependency 
plugin showed nothing useful.


How do I debug this?


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Debugging Maven error settings [m2]

2007-11-28 Thread Chris Helck

I am having trouble understanding the error below. Maven seems unable to
pull things down from the central repo, and I don't know why. 

I can connect to the repo via the web. 
I have deleted by ~/.m2/repository directory. 
The plugin-registry.xml files do not exist.
I have been playing with the settings.xml files, but I think I've undone
my changes. I would like to run the goal help:effective-settings, but I
can't download the maven help plugin. Catch-22.

Any ideas about what is going on? Or how to debug this type of
situation?


%
+ Error stacktraces are turned on.
Maven version: 2.0.7
Java version: 1.6.0_03
OS name: linux version: 2.6.22-14-386 arch: i386
[DEBUG] Building Maven user-level plugin registry from:
'/home/chelck/.m2/plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'/home/chelck/maven-2.0.7/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]


[INFO] Building parent pom
[INFO]task-segment: [test]
[INFO]


[DEBUG] maven-compiler-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
latest version

  org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST


[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST
[DEBUG] maven-compiler-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
release version

  org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE


[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does
not exist or no valid version could be found
[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no
valid version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1286)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl
e(DefaultLifecycleExecutor.java:1221)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:987)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:143)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.plugin.version.PluginVersionNotFoundException: The
plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist
or no valid version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:228)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:90)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
anager.java:166)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1257)
... 17 more
[INFO]

[INFO] Total time:  1 second
[INFO] Finished at: Wed Nov 28 14:52:53 GMT 2007
[INFO] Final Memory: 1M/4M
[INFO] ---
%-

Thanks,
Christopher Helck

Re: Debugging Maven error settings [m2]

2007-11-28 Thread Wendy Smoak

On Nov 28, 2007 8:05 AM, Chris Helck [EMAIL PROTECTED] wrote:
 I am having trouble understanding the error below. Maven seems unable to
 pull things down from the central repo, and I don't know why.

 I can connect to the repo via the web.
 I have deleted by ~/.m2/repository directory.
 The plugin-registry.xml files do not exist.
 I have been playing with the settings.xml files, but I think I've undone
 my changes. I would like to run the goal help:effective-settings, but I
 can't download the maven help plugin. Catch-22.

 Any ideas about what is going on? Or how to debug this type of
 situation?

You may be running into the default once-per-day check for updates.
If it fails once, Maven won't check [that repository for that plugin]
again until tommorrow.

Try adding -U to the command line.  (Or deleting the plugin directory
from your local repo.)

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Debugging Maven error settings [m2]

2007-11-28 Thread Chris Helck

No this doesn't help. Is there anyway to see which repos maven is
checking?

Thanks,
Chris 

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 28, 2007 10:13 AM
To: Maven Users List
Subject: Re: Debugging Maven error settings [m2]

On Nov 28, 2007 8:05 AM, Chris Helck [EMAIL PROTECTED] wrote:
 I am having trouble understanding the error below. Maven seems unable 
 to pull things down from the central repo, and I don't know why.

 I can connect to the repo via the web.
 I have deleted by ~/.m2/repository directory.
 The plugin-registry.xml files do not exist.
 I have been playing with the settings.xml files, but I think I've 
 undone my changes. I would like to run the goal 
 help:effective-settings, but I can't download the maven help plugin.
Catch-22.

 Any ideas about what is going on? Or how to debug this type of 
 situation?

You may be running into the default once-per-day check for updates.
If it fails once, Maven won't check [that repository for that plugin]
again until tommorrow.

Try adding -U to the command line.  (Or deleting the plugin directory
from your local repo.)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

**
This communication and all information (including, but not limited to,
 market prices/levels and data) contained therein (the Information) is
 for informational purposes only, is confidential, may be legally
 privileged and is the intellectual property of ICAP plc and its affiliates
 (ICAP) or third parties. No confidentiality or privilege is waived or
 lost by any mistransmission. The Information is not, and should not
 be construed as, an offer, bid or solicitation in relation to any
 financial instrument or as an official confirmation of any transaction.
 The Information is not warranted, including, but not limited, as to
 completeness, timeliness or accuracy and is subject to change
 without notice. ICAP assumes no liability for use or misuse of the
 Information. All representations and warranties are expressly
 disclaimed. The Information does not necessarily reflect the views of
 ICAP. Access to the Information by anyone else other than the
 recipient is unauthorized and any disclosure, copying, distribution or
 any action taken or omitted to be taken in reliance on it is prohibited. If
 you receive this message in error, please immediately delete it and all
 copies of it from your system, destroy any hard copies of it and
 notify the sender.
**

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debugging Maven error settings [m2]

2007-11-28 Thread Wayne Fay

Assuming you have nothing special in your settings.xml or your hosts
file that would redirect things, a simple mvn help:effective-pom
should give you an idea as to what repos are being searched.

If you do have mirrors etc in settings.xml which complicate things, or
you just can't figure it out, then you might want to use a TCP/IP
analzer like Ethereal.

Wayne

On 11/28/07, Chris Helck [EMAIL PROTECTED] wrote:
 No this doesn't help. Is there anyway to see which repos maven is
 checking?

 Thanks,
 Chris

 -Original Message-
 From: Wendy Smoak [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, November 28, 2007 10:13 AM
 To: Maven Users List
 Subject: Re: Debugging Maven error settings [m2]

 On Nov 28, 2007 8:05 AM, Chris Helck [EMAIL PROTECTED] wrote:
  I am having trouble understanding the error below. Maven seems unable
  to pull things down from the central repo, and I don't know why.
 
  I can connect to the repo via the web.
  I have deleted by ~/.m2/repository directory.
  The plugin-registry.xml files do not exist.
  I have been playing with the settings.xml files, but I think I've
  undone my changes. I would like to run the goal
  help:effective-settings, but I can't download the maven help plugin.
 Catch-22.
 
  Any ideas about what is going on? Or how to debug this type of
  situation?

 You may be running into the default once-per-day check for updates.
 If it fails once, Maven won't check [that repository for that plugin]
 again until tommorrow.

 Try adding -U to the command line.  (Or deleting the plugin directory
 from your local repo.)

 --
 Wendy

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 **
 This communication and all information (including, but not limited to,
  market prices/levels and data) contained therein (the Information) is
  for informational purposes only, is confidential, may be legally
  privileged and is the intellectual property of ICAP plc and its affiliates
  (ICAP) or third parties. No confidentiality or privilege is waived or
  lost by any mistransmission. The Information is not, and should not
  be construed as, an offer, bid or solicitation in relation to any
  financial instrument or as an official confirmation of any transaction.
  The Information is not warranted, including, but not limited, as to
  completeness, timeliness or accuracy and is subject to change
  without notice. ICAP assumes no liability for use or misuse of the
  Information. All representations and warranties are expressly
  disclaimed. The Information does not necessarily reflect the views of
  ICAP. Access to the Information by anyone else other than the
  recipient is unauthorized and any disclosure, copying, distribution or
  any action taken or omitted to be taken in reliance on it is prohibited. If
  you receive this message in error, please immediately delete it and all
  copies of it from your system, destroy any hard copies of it and
  notify the sender.
 **


 -
 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]

Re: Debugging Maven in Netbeans

2007-09-25 Thread Ravi Luthra

I get the same Exception when I try to set a main class in the
properties of a project. Almost all of the projects I open are not
created from the archetype, but custom edited.
Same configuration too 5.5.1 and latest Mevenide listed on the
Mevenide 2 website.

I actually upgraded from 5.5 to see if this problem would go away. It didn't..

Should I upgrade to 6.0?

Ravi

On 9/5/07, Milos Kleint [EMAIL PROTECTED] wrote:
I've checked the stacktrace and it's not clear to me how a NPE could
get there. Does it happen for you all the time? can you try on a
sample quickstart project created from archetype?
I'm personally using Nb 6.0 + mevenide 3.0.x (close to what ships on
netbeans AU for milestone 10) and use this feature occationally. This
code is almost the same.

Not sure if pasting the pom snippet is enough. an assempty descriptor
is also generated and you might be missing that one tool. Maybe I can
send you a zipped sample project privately?

Milos

On 9/5/07, Demian Mrakovich [EMAIL PROTECTED] wrote:

Now, that would be great - if it worked.

When trying this in Netbeans 5.5.1, Maven 2 project support 2.3.4:

java.lang.NullPointerException
at
org.codehaus.mevenide.netbeans.customizer.RunJarPanel.checkAssemblyPlugin(RunJarPanel.java:337)
at
org.codehaus.mevenide.netbeans.customizer.RunJarPanel.applyChanges(RunJarPanel.java:274)
at
org.codehaus.mevenide.netbeans.customizer.CustomizerProviderImpl$OptionListener.actionPerformed(CustomizerProviderImpl.java:236)
at
org.netbeans.modules.project.uiapi.CustomizerDialog$OptionListener.actionPerformed(CustomizerDialog.java:162)
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
..

Anyone care to share the actual XML for pom.xml?

Milos Kleint wrote:

that's in project's popup menu. last item on the list.. Properties..
there in Run tab, you set the main class.

Milos

On 8/28/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,

I have opened few maven project. I use NB6 Ms10 with external maven build
enabled. The maven version I have is 2.0.7. I am able to compile( mvn
install) the project. Now when I try to execute the same I get the
following message.

In order to run the project, Netbeans needs a custom profile in your
pom.xml . To create and customise the profile, go to the project's
Properties dialog and update the Run Panel.

I can see profiles tag in settings.xml but nothing in pom.xml. Any help
appretiated. I want to run the programs in debug mode to understand what
happens.

Thanks Regards,
Jayaram

--
View this message in context:
http://www.nabble.com/Debugging-Maven-in-Netbeans-tf4341676s177.html#a12495884
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debugging Maven in Netbeans

2007-09-25 Thread Milos Kleint

Ravi Luthra wrote:

I actually upgraded from 5.5 to see if this problem would go away. It didn't..

Should I upgrade to 6.0?

yes. beta one has it fixed.

Milos

Ravi

On 9/5/07, Milos Kleint [EMAIL PROTECTED] wrote:

I've checked the stacktrace and it's not clear to me how a NPE could
get there. Does it happen for you all the time? can you try on a
sample quickstart project created from archetype?
I'm personally using Nb 6.0 + mevenide 3.0.x (close to what ships on
netbeans AU for milestone 10) and use this feature occationally. This
code is almost the same.

Not sure if pasting the pom snippet is enough. an assempty descriptor
is also generated and you might be missing that one tool. Maybe I can
send you a zipped sample project privately?

Milos

On 9/5/07, Demian Mrakovich [EMAIL PROTECTED] wrote:

Now, that would be great - if it worked.

When trying this in Netbeans 5.5.1, Maven 2 project support 2.3.4:

Anyone care to share the actual XML for pom.xml?

Milos Kleint wrote:

that's in project's popup menu. last item on the list.. Properties..
there in Run tab, you set the main class.

Milos

On 8/28/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:

Hi,

In order to run the project, Netbeans needs a custom profile in your
pom.xml . To create and customise the profile, go to the project's
Properties dialog and update the Run Panel.

I can see profiles tag in settings.xml but nothing in pom.xml. Any help
appretiated. I want to run the programs in debug mode to understand what
happens.

Thanks Regards,
Jayaram

--
View this message in context:
http://www.nabble.com/Debugging-Maven-in-Netbeans-tf4341676s177.html#a12495884
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debugging Maven in Netbeans

2007-09-05 Thread Demian Mrakovich

Now, that would be great - if it worked.

When trying this in Netbeans 5.5.1, Maven 2 project support 2.3.4:

Anyone care to share the actual XML for pom.xml?

Milos Kleint wrote:

that's in project's popup menu. last item on the list.. Properties..
there in Run tab, you set the main class.

Milos

On 8/28/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,

In order to run the project, Netbeans needs a custom profile in your
pom.xml . To create and customise the profile, go to the project's
Properties dialog and update the Run Panel.

I can see profiles tag in settings.xml but nothing in pom.xml. Any help
appretiated. I want to run the programs in debug mode to understand what
happens.

Thanks Regards,
Jayaram

--
View this message in context:
http://www.nabble.com/Debugging-Maven-in-Netbeans-tf4341676s177.html#a12495884
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debugging Maven in Netbeans

2007-09-05 Thread Milos Kleint

Not sure if pasting the pom snippet is enough. an assempty descriptor
is also generated and you might be missing that one tool. Maybe I can
send you a zipped sample project privately?

Milos

On 9/5/07, Demian Mrakovich [EMAIL PROTECTED] wrote:

Now, that would be great - if it worked.

When trying this in Netbeans 5.5.1, Maven 2 project support 2.3.4:

Anyone care to share the actual XML for pom.xml?

Milos Kleint wrote:

that's in project's popup menu. last item on the list.. Properties..
there in Run tab, you set the main class.

Milos

On 8/28/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,

In order to run the project, Netbeans needs a custom profile in your
pom.xml . To create and customise the profile, go to the project's
Properties dialog and update the Run Panel.

I can see profiles tag in settings.xml but nothing in pom.xml. Any help
appretiated. I want to run the programs in debug mode to understand what
happens.

Thanks Regards,
Jayaram

--
View this message in context:
http://www.nabble.com/Debugging-Maven-in-Netbeans-tf4341676s177.html#a12495884
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debugging Maven in Netbeans

2007-08-28 Thread Milos Kleint

that's in project's popup menu. last item on the list.. Properties..
there in Run tab, you set the main class.

Milos

On 8/28/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 Hi,

 I have opened few maven project. I use NB6 Ms10 with external maven build
 enabled. The maven version I have is 2.0.7. I am able to compile( mvn
 install) the project. Now when I try to execute the same I get the
 following message.

 In order to run the project, Netbeans needs a custom profile in your
 pom.xml . To create and customise the profile, go to the project's
 Properties dialog and update the Run Panel.

 I can see profiles tag in settings.xml but nothing in pom.xml. Any help
 appretiated. I want to run the programs in debug mode to understand what
 happens.


 Thanks  Regards,
 Jayaram

 This communication is for informational purposes only. It is not
 intended as an offer or solicitation for the purchase or sale of
 any financial instrument or as an official confirmation of any
 transaction. All market prices, data and other information are not
 warranted as to completeness or accuracy and are subject to change
 without notice. Any comments or statements made herein do not
 necessarily reflect those of JPMorgan Chase  Co., its subsidiaries
 and affiliates. This transmission may contain information that is
 privileged, confidential, legally privileged, and/or exempt from
 disclosure under applicable law. If you are not the intended
 recipient, you are hereby notified that any disclosure, copying,
 distribution, or use of the information contained herein (including
 any reliance thereon) is STRICTLY PROHIBITED. Although this
 transmission and any attachments are believed to be free of any
 virus or other defect that might affect any computer system into
 which it is received and opened, it is the responsibility of the
 recipient to ensure that it is virus free and no responsibility is
 accepted by JPMorgan Chase  Co., its subsidiaries and affiliates,
 as applicable, for any loss or damage arising in any way from its
 use. If you received this transmission in error, please immediately
 contact the sender and destroy the material in its entirety,
 whether in electronic or hard copy format. Thank you.
 Please refer to http://www.jpmorgan.com/pages/disclosures for
 disclosures relating to UK legal entities.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Debugging Maven in Netbeans

2007-08-28 Thread jayaram . x . ganapathy

Hi,

I have opened few maven project. I use NB6 Ms10 with external maven build 
enabled. The maven version I have is 2.0.7. I am able to compile( mvn 
install) the project. Now when I try to execute the same I get the 
following message.

In order to run the project, Netbeans needs a custom profile in your 
pom.xml . To create and customise the profile, go to the project's 
Properties dialog and update the Run Panel.

I can see profiles tag in settings.xml but nothing in pom.xml. Any help 
appretiated. I want to run the programs in debug mode to understand what 
happens.


Thanks  Regards, 
Jayaram

This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase  Co., its subsidiaries
and affiliates. This transmission may contain information that is
privileged, confidential, legally privileged, and/or exempt from
disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. Although this
transmission and any attachments are believed to be free of any
virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the
recipient to ensure that it is virus free and no responsibility is
accepted by JPMorgan Chase  Co., its subsidiaries and affiliates,
as applicable, for any loss or damage arising in any way from its
use. If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you. 
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

Re: Debugging maven within eclipse

2007-06-07 Thread Nenad Jaksic

Your M2_HOME should point to directory where maven repository is located 
Than can be any location or .m2 directory as suggested in installation guide.
Hope this helps

 http://docs.codehaus.org/display/MAVENUSER/Dealing+with+Eclipse-based+IDE
 
 On 6/6/07, Graham Leggett [EMAIL PROTECTED] wrote:
  Hi all,
 
  In order to get to the bottom of a number of maven issues, I would like to
  fire up maven inside eclipse so that I can do step by step debugging, and
  having gone through the docs I am struggling to find out how to do this.
 
  Google found this:
  http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Plugin+inside+Eclipse
  which describes how one might remotely connect to a maven instance to
  debug it, but using this method requires an M2_HOME, and it's not clear as
  to where this environment variable should be pointed to.
 
  Is there a howto on this anywhere?
 
  Regards,
  Graham
  --
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -- 
 Karan Malhi
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

Debugging maven within eclipse

2007-06-06 Thread Graham Leggett

Hi all,

In order to get to the bottom of a number of maven issues, I would like to
fire up maven inside eclipse so that I can do step by step debugging, and
having gone through the docs I am struggling to find out how to do this.

Google found this:
http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Plugin+inside+Eclipse
which describes how one might remotely connect to a maven instance to
debug it, but using this method requires an M2_HOME, and it's not clear as
to where this environment variable should be pointed to.

Is there a howto on this anywhere?

Regards,
Graham
--



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debugging maven within eclipse

2007-06-06 Thread Karan Malhi


http://docs.codehaus.org/display/MAVENUSER/Dealing+with+Eclipse-based+IDE

On 6/6/07, Graham Leggett [EMAIL PROTECTED] wrote:

Hi all,

In order to get to the bottom of a number of maven issues, I would like to
fire up maven inside eclipse so that I can do step by step debugging, and
having gone through the docs I am struggling to find out how to do this.

Google found this:
http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Plugin+inside+Eclipse
which describes how one might remotely connect to a maven instance to
debug it, but using this method requires an M2_HOME, and it's not clear as
to where this environment variable should be pointed to.

Is there a howto on this anywhere?

Regards,
Graham
--



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Karan Malhi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Debugging Maven

2006-11-07 Thread Deluigi Marcus

Hi

I am quite new to Maven and I need to understand a quite large project
which also happened to have a broken maven build cycle.

Is there any way to:
* list all user-defined goals for each phase
* list all used plugins
* determine which of their goals are used for which phase
* skip a phase / goal

There are 112 poms and the effective pom has 113177 lines, so I prefer
to first retrieve a high-level abstraction.

It seems as if the pre-integration-test phase is broken, so skipping a
phase would be quite useful to get a basis work and then proceed to less
serious problems.

Greetings
Marcus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Debugging maven projects using eclipse/tomcat5

2004-12-07 Thread Duncan Krebs

Hi,
I have a maven project that is a tomcat5 webapp and I'm using war:inplace to 
set things up so I can code and debug at the same time. For organization I have 
a couple of other maven projects that are separate but referenced by my webapp. 
I have the reference setup by using snapshot dependencies in the project.xml of 
the webapp. 

I'm trying to figure out how I can make changes to the projects referenced by 
the webapp in eclipse and then have tomcat5 recognize the change and reload the 
context. I imagine to do this I'd have to define the reference to these 
projects in a different way and also change their target path somewhere in the 
WEB-INF folder of the webapp. The only problem here though is eclipse will wipe 
out other classes in the bin that should not be deleted.  Any ideas or is this 
not making sense? - Duncan

39 matches

Mail list logo