Re: Documentation (wrongly?) says Maven 3.3.1 runs with Java 1.6

2015-03-19 Thread Anders Hammar
MNG-5789 created to monitor this.
Thanks for reporting!

/Anders

On Thu, Mar 19, 2015 at 8:52 AM, Arend v. Reinersdorff ar...@arendvr.com
wrote:

 ok, thanks for the clarification.

 The system requirements on the download page are correct now.
 But the README.txt in the distribution is still wrong.

 Regards,
 Arend


 On Wed, Mar 18, 2015 at 2:54 PM, Jason van Zyl ja...@takari.io wrote:

  Olivier fixed the doco so that should do out shortly.
 
  On Mar 18, 2015, at 9:48 AM, Anders Hammar and...@hammar.net wrote:
 
   That is correct, the docs haven't been updated. Maven 3.3+ requires JDK
  1.7.
  
   /Anders (mobile)
   Den 18 mar 2015 09:37 skrev Arend v. Reinersdorff ar...@arendvr.com
 :
  
   Hi,
  
   Maven 3.3.1 requires Java 1.7:
   - [MNG-5780] - upgrade Java minimum version prerequisite from Java 6
 to
   Java 7
   - When I try to run Maven 3.3.1 with Java 1.6 I get the exception:
   Exception in thread main java.lang.UnsupportedClassVersionError:
   org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
  
  
   But the documentation says the system requirements are still at Java
  1.6:
   - On the download page:
  http://maven.apache.org/download.cgi#Requirements
   - In README.txt when downloading Maven 3.3.1:
System Requirements
---
JDK:
  1.6 or above (this is to execute Maven - it still allows you to
 build
   against 1.3
  and prior JDK's).
  
   I assume the requirement is really Java 1.7 but the documentation has
  not
   been updated?
  
   Regards,
   Arend
  
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  happiness is like a butterfly: the more you chase it, the more it will
  elude you, but if you turn your attention to other things, it will come
  and sit softly on your shoulder ...
 
  -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 



Re: Documentation (wrongly?) says Maven 3.3.1 runs with Java 1.6

2015-03-19 Thread Arnaud Héritier
I'm a little bit lost with the download page
Several time it references Maven 3.2 but this one isn't available any more
(only in archives)
But 3.2 is the one to use for Java 6 users ? (If we exclude the usage of
toolschain)
I'm not sure why we are keeping 3.0, 3.1 and not 3.2

On Thu, Mar 19, 2015 at 10:05 AM, Anders Hammar and...@hammar.net wrote:

 MNG-5789 created to monitor this.
 Thanks for reporting!

 /Anders

 On Thu, Mar 19, 2015 at 8:52 AM, Arend v. Reinersdorff ar...@arendvr.com
 wrote:

  ok, thanks for the clarification.
 
  The system requirements on the download page are correct now.
  But the README.txt in the distribution is still wrong.
 
  Regards,
  Arend
 
 
  On Wed, Mar 18, 2015 at 2:54 PM, Jason van Zyl ja...@takari.io wrote:
 
   Olivier fixed the doco so that should do out shortly.
  
   On Mar 18, 2015, at 9:48 AM, Anders Hammar and...@hammar.net wrote:
  
That is correct, the docs haven't been updated. Maven 3.3+ requires
 JDK
   1.7.
   
/Anders (mobile)
Den 18 mar 2015 09:37 skrev Arend v. Reinersdorff 
 ar...@arendvr.com
  :
   
Hi,
   
Maven 3.3.1 requires Java 1.7:
- [MNG-5780] - upgrade Java minimum version prerequisite from Java 6
  to
Java 7
- When I try to run Maven 3.3.1 with Java 1.6 I get the exception:
Exception in thread main java.lang.UnsupportedClassVersionError:
org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
   
   
But the documentation says the system requirements are still at Java
   1.6:
- On the download page:
   http://maven.apache.org/download.cgi#Requirements
- In README.txt when downloading Maven 3.3.1:
 System Requirements
 ---
 JDK:
   1.6 or above (this is to execute Maven - it still allows you to
  build
against 1.3
   and prior JDK's).
   
I assume the requirement is really Java 1.7 but the documentation
 has
   not
been updated?
   
Regards,
Arend
   
  
   Thanks,
  
   Jason
  
   --
   Jason van Zyl
   Founder, Takari and Apache Maven
   http://twitter.com/jvanzyl
   http://twitter.com/takari_io
   -
  
   happiness is like a butterfly: the more you chase it, the more it will
   elude you, but if you turn your attention to other things, it will come
   and sit softly on your shoulder ...
  
   -- Thoreau
  
  
  
  
  
  
  
  
  
  
  
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
 




-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier


AW: AW: mvn clean package requests access rights for local Nexus repository

2015-03-19 Thread Markus Karg
As I said I cannot reproduce the bug anymore, so do you think the requested 
test makes any sense still?


-Ursprüngliche Nachricht-
Von: Martin Gainty [mailto:mgai...@hotmail.com] 
Gesendet: Donnerstag, 19. März 2015 02:04
An: users@maven.apache.org
Betreff: RE: AW: mvn clean package requests access rights for local Nexus 
repository

as bernd suggested can you view possible access when you enable -X?
might also help to see extension errors with -e mvn -e -X package  package.out 
can we view package.out?

I would be interested looking at the netstat deltas specifically
shnetstat -a   netstat_before.log
run command
shmvn -X package

run another shell and view any new network connections
netstat -a  netstat_after.log

any deltas between netstat_before.log and netstat_after.log can you display 
both here so we can diff the 2 files?
?
Martin


 From: k...@quipsy.de
 To: users@maven.apache.org
 Date: Wed, 18 Mar 2015 16:42:06 +0100
 Subject: AW: mvn clean package requests access rights for local 
 Nexus repository
 
 Bernd,
 
 your theory failed the test:
 
 * Unplugged USB stick, so Maven has no passwords anymore
 * Removed .m2\repository folder from disk, so Maven is enforced to 
 download rather everything newly from our Nexus mirror
 * mvn clean package built maven-dependency-plugin without any 
 problem
 
 Conclusion: It is definitively NOT a download problem, but still supports my 
 theory that maven-dependency-plugin wants to UPLOAD something at package 
 phase.
 
 If I just would have kept the protocol earlier today, I could tell you 
 what thing actually it was... :-(
 
 Regards
 -Markus
 
 
 -Ursprüngliche Nachricht-
 Von: Bernd [mailto:e...@zusammenkunft.net]
 Gesendet: Mittwoch, 18. März 2015 14:27
 An: Maven Users List
 Betreff: Re: mvn clean package requests access rights for local 
 Nexus repository
 
 Hello,
 
 It sounds more like a download as it does not ask again. You can wipe your 
 local repo cache (or use a different one in settings.xml) and try to 
 reproduce the problem. If you run with -X and actually keep the maven log 
 output you should be able to see the access in question.
 
 Gruss
 Bernd
 Am 18.03.2015 14:02 schrieb Markus Karg k...@quipsy.de:
 
  Dear Maven Experts,
 
  just did svn checkout to get trunk of maven-dependency-plugin, and 
  wanted to build it using mvn clean package. What then happened is 
  really
  scary:
 
 
  * It complained about missing access on that path where my USB
  stick stores the encrypted password for my local Nexus repository.
 
  * My local Nexus repository is a mirror of central with public
  access, only demanding passwords for uploads.
 
  * I plugged in my stick, did mvn clean package again, and it
  worked pretty well.
 
  * REMOVED my stick, and since then mvn clean package works
  without, still!
 
  That looks if packaging maven-dependency-plugin would need to 
  WRITE into my Nexus (possibly central?) at package phase, if a 
  particular thing is not found there.
 
  This is scary, as nobody expects UPLOADS are done at packaging.
 
  If somebody has an explanation why that happens, I'd ask him to 
  publish here, so everybody will understand the reason for this! :)
 
  Regards
  -Markus
 
 
 
 B KKK
 KCB  [  X  ܚX KK[XZ[
 \ \  ][  X  ܚX PX] [  \X K ܙ B  ܈Y][
 ۘ[  [X[  K[XZ[
 \ \  Z[X] [  \X K ܙ B
  

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


Re: Documentation (wrongly?) says Maven 3.3.1 runs with Java 1.6

2015-03-19 Thread Arend v. Reinersdorff
ok, thanks for the clarification.

The system requirements on the download page are correct now.
But the README.txt in the distribution is still wrong.

Regards,
Arend


On Wed, Mar 18, 2015 at 2:54 PM, Jason van Zyl ja...@takari.io wrote:

 Olivier fixed the doco so that should do out shortly.

 On Mar 18, 2015, at 9:48 AM, Anders Hammar and...@hammar.net wrote:

  That is correct, the docs haven't been updated. Maven 3.3+ requires JDK
 1.7.
 
  /Anders (mobile)
  Den 18 mar 2015 09:37 skrev Arend v. Reinersdorff ar...@arendvr.com:
 
  Hi,
 
  Maven 3.3.1 requires Java 1.7:
  - [MNG-5780] - upgrade Java minimum version prerequisite from Java 6 to
  Java 7
  - When I try to run Maven 3.3.1 with Java 1.6 I get the exception:
  Exception in thread main java.lang.UnsupportedClassVersionError:
  org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
 
 
  But the documentation says the system requirements are still at Java
 1.6:
  - On the download page:
 http://maven.apache.org/download.cgi#Requirements
  - In README.txt when downloading Maven 3.3.1:
   System Requirements
   ---
   JDK:
 1.6 or above (this is to execute Maven - it still allows you to build
  against 1.3
 and prior JDK's).
 
  I assume the requirement is really Java 1.7 but the documentation has
 not
  been updated?
 
  Regards,
  Arend
 

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will come
 and sit softly on your shoulder ...

 -- Thoreau













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




Re: Documentation (wrongly?) says Maven 3.3.1 runs with Java 1.6

2015-03-19 Thread Arnaud Héritier
Hi,

  I tested 3.3 a little bit and didn't find any issue
  But it requires Java 7 if you need to build with an older version of Java
you'll have to setup a toolchain
  You can always find old releases from :
http://archive.apache.org/dist/maven/maven-3/
http://archive.apache.org/dist/maven/binaries/


cheers

On Thu, Mar 19, 2015 at 11:23 AM, Björn Raupach 
raupach.bjo...@googlemail.com wrote:

 Hi group,

 I have the same problem. Looking for the 3.2.x releases. Can’t upgrade to
 3.3.x yet.

 Or is it save to skip 3.2.x for now?

 /Björn

  On 19 Mar 2015, at 11:01 , Arnaud Héritier aherit...@gmail.com wrote:
 
  I'm a little bit lost with the download page
  Several time it references Maven 3.2 but this one isn't available any
 more
  (only in archives)
  But 3.2 is the one to use for Java 6 users ? (If we exclude the usage of
  toolschain)
  I'm not sure why we are keeping 3.0, 3.1 and not 3.2
 
  On Thu, Mar 19, 2015 at 10:05 AM, Anders Hammar and...@hammar.net
 wrote:
 
  MNG-5789 created to monitor this.
  Thanks for reporting!
 
  /Anders
 
  On Thu, Mar 19, 2015 at 8:52 AM, Arend v. Reinersdorff 
 ar...@arendvr.com
  wrote:
 
  ok, thanks for the clarification.
 
  The system requirements on the download page are correct now.
  But the README.txt in the distribution is still wrong.
 
  Regards,
  Arend
 
 
  On Wed, Mar 18, 2015 at 2:54 PM, Jason van Zyl ja...@takari.io
 wrote:
 
  Olivier fixed the doco so that should do out shortly.
 
  On Mar 18, 2015, at 9:48 AM, Anders Hammar and...@hammar.net wrote:
 
  That is correct, the docs haven't been updated. Maven 3.3+ requires
  JDK
  1.7.
 
  /Anders (mobile)
  Den 18 mar 2015 09:37 skrev Arend v. Reinersdorff 
  ar...@arendvr.com
  :
 
  Hi,
 
  Maven 3.3.1 requires Java 1.7:
  - [MNG-5780] - upgrade Java minimum version prerequisite from Java 6
  to
  Java 7
  - When I try to run Maven 3.3.1 with Java 1.6 I get the exception:
  Exception in thread main java.lang.UnsupportedClassVersionError:
  org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
 
 
  But the documentation says the system requirements are still at Java
  1.6:
  - On the download page:
  http://maven.apache.org/download.cgi#Requirements
  - In README.txt when downloading Maven 3.3.1:
  System Requirements
  ---
  JDK:
1.6 or above (this is to execute Maven - it still allows you to
  build
  against 1.3
and prior JDK's).
 
  I assume the requirement is really Java 1.7 but the documentation
  has
  not
  been updated?
 
  Regards,
  Arend
 
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  happiness is like a butterfly: the more you chase it, the more it will
  elude you, but if you turn your attention to other things, it will
 come
  and sit softly on your shoulder ...
 
  -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
 
 
 
  --
  -
  Arnaud Héritier
  http://aheritier.net
  Mail/GTalk: aheritier AT gmail DOT com
  Twitter/Skype : aheritier

 -BEGIN PGP PUBLIC KEY BLOCK-
 Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
 Comment: GPGTools - http://gpgtools.org

 mQENBE04AUEBCAC5Bu91Mtbjo7dnYWli6c7BMExsND8x+IsHazbGwQ/UAw0RY5hm
 rAkrxLYams2E/AsTq3FEdHExeLFei7BOdjNgg7iMvozcB2C5PTHSQyBpqbgF5/zo
 /eN7Rj5yl/r4AddGhpp88jg7B9PkF/Vs2ZPDACxVxXtDVp+//6pp/DTLohLIhx7j
 X1V2VDvbg9G3cFRHqng6qX/yXP0Zgy42ISd5qFQQP8tTZMt/ocN7+XeLT/JFkWNQ
 lAcORZ8/On7szNeqU3iqUrwvFu5tH2BkVbvL2/sV+TXsppbLR5trSMKChAXx/xR1
 7oa2I0raXg0dKsIAN+Zp9FvIMvBbd2KihjbjABEBAAG0LkJqb2VybiBSYXVwYWNo
 IDxyYXVwYWNoLmJqb2VybkBnb29nbGVtYWlsLmNvbT6JATgEEwECACIFAk04AUEC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEHyO/bs4ZyFdStwH/2s1zaz0
 NJcwF1PloylFngNlSTXCuMjj3HupUGfOygQJwWN3Ta1fv2vkmVPpT+0D+Ht3zopA
 P/039qgrMtQoIIUbVnHjykfb/bQmJWtB9VqDbBe/rWytaSpEiJvrD3NiRVLGpjHe
 P5Cwg6ayBEWrZo+79BlmXcurZp3L2X6V+0SensAQFpKIpPa8k4lHLjsRzTq8lkta
 2ORCvy9pmsWv91SmFXrcBv/mpSoZ8svbUvbJJulzmrVQUQE5s5BW7n46EbqmVqJR
 Th3SkIQtwC0Hs945p25hgK80dBQSHqP6P4lrnrFo6TCbnLMcAdd0scPa9kJmrnvv
 yHUmK8EffB5400i5AQ0ETTgBQQEIAPXiOZgblIz1wFuaxeaBGS3A37lFgpffm0Dl
 jofMC/B1i4BSZHz0U5NO7O1KJ3afRSU74ffCUmANIM+O9SopA8zlW/clSig9IRJj
 sYpi84OCsPT1kCMKpRARYChEPspitDeasrUmDQ3MbgH8vT0t2HWHEQdy4huGhBKm
 stm4eV331i7AMbhy3zspZYVbfMz3qV3WVf8g1wGiNadCjBTl8sbzlW5IaJFFV+Fx
 Ij6yzcco+1onHirxHm9Zdp/91hBZEiHbEAiGmKW6YIPvdLDITlFeRLf+X9D7/wpA
 ebAqr0Ta4g2XXCdwqwS6bakTOftvUB4wAnh7jDFsF7diLMbc8C8AEQEAAYkBHwQY
 AQIACQUCTTgBQQIbDAAKCRB8jv27OGchXSK4B/4pwSVL4fhJvwHh9eT40CD6D80D
 3gg6l2BpYCs/pfvM+zfC0pP7YTZpTK+EXlC6SdralurYg4IgODQ1QijpG8j9jh09
 Zb74SlLpZrrsB4jSXRrl/QHfFPdbZ7ONW8cRrNrrguCuVv6x0xCWkBzS+GyJKSUP
 

Re: Documentation (wrongly?) says Maven 3.3.1 runs with Java 1.6

2015-03-19 Thread Björn Raupach
Hi group,

I have the same problem. Looking for the 3.2.x releases. Can’t upgrade to 3.3.x 
yet.

Or is it save to skip 3.2.x for now?

/Björn

 On 19 Mar 2015, at 11:01 , Arnaud Héritier aherit...@gmail.com wrote:
 
 I'm a little bit lost with the download page
 Several time it references Maven 3.2 but this one isn't available any more
 (only in archives)
 But 3.2 is the one to use for Java 6 users ? (If we exclude the usage of
 toolschain)
 I'm not sure why we are keeping 3.0, 3.1 and not 3.2
 
 On Thu, Mar 19, 2015 at 10:05 AM, Anders Hammar and...@hammar.net wrote:
 
 MNG-5789 created to monitor this.
 Thanks for reporting!
 
 /Anders
 
 On Thu, Mar 19, 2015 at 8:52 AM, Arend v. Reinersdorff ar...@arendvr.com
 wrote:
 
 ok, thanks for the clarification.
 
 The system requirements on the download page are correct now.
 But the README.txt in the distribution is still wrong.
 
 Regards,
 Arend
 
 
 On Wed, Mar 18, 2015 at 2:54 PM, Jason van Zyl ja...@takari.io wrote:
 
 Olivier fixed the doco so that should do out shortly.
 
 On Mar 18, 2015, at 9:48 AM, Anders Hammar and...@hammar.net wrote:
 
 That is correct, the docs haven't been updated. Maven 3.3+ requires
 JDK
 1.7.
 
 /Anders (mobile)
 Den 18 mar 2015 09:37 skrev Arend v. Reinersdorff 
 ar...@arendvr.com
 :
 
 Hi,
 
 Maven 3.3.1 requires Java 1.7:
 - [MNG-5780] - upgrade Java minimum version prerequisite from Java 6
 to
 Java 7
 - When I try to run Maven 3.3.1 with Java 1.6 I get the exception:
 Exception in thread main java.lang.UnsupportedClassVersionError:
 org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
 
 
 But the documentation says the system requirements are still at Java
 1.6:
 - On the download page:
 http://maven.apache.org/download.cgi#Requirements
 - In README.txt when downloading Maven 3.3.1:
 System Requirements
 ---
 JDK:
   1.6 or above (this is to execute Maven - it still allows you to
 build
 against 1.3
   and prior JDK's).
 
 I assume the requirement is really Java 1.7 but the documentation
 has
 not
 been updated?
 
 Regards,
 Arend
 
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will come
 and sit softly on your shoulder ...
 
 -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
 
 
 
 -- 
 -
 Arnaud Héritier
 http://aheritier.net
 Mail/GTalk: aheritier AT gmail DOT com
 Twitter/Skype : aheritier

-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

mQENBE04AUEBCAC5Bu91Mtbjo7dnYWli6c7BMExsND8x+IsHazbGwQ/UAw0RY5hm
rAkrxLYams2E/AsTq3FEdHExeLFei7BOdjNgg7iMvozcB2C5PTHSQyBpqbgF5/zo
/eN7Rj5yl/r4AddGhpp88jg7B9PkF/Vs2ZPDACxVxXtDVp+//6pp/DTLohLIhx7j
X1V2VDvbg9G3cFRHqng6qX/yXP0Zgy42ISd5qFQQP8tTZMt/ocN7+XeLT/JFkWNQ
lAcORZ8/On7szNeqU3iqUrwvFu5tH2BkVbvL2/sV+TXsppbLR5trSMKChAXx/xR1
7oa2I0raXg0dKsIAN+Zp9FvIMvBbd2KihjbjABEBAAG0LkJqb2VybiBSYXVwYWNo
IDxyYXVwYWNoLmJqb2VybkBnb29nbGVtYWlsLmNvbT6JATgEEwECACIFAk04AUEC
GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEHyO/bs4ZyFdStwH/2s1zaz0
NJcwF1PloylFngNlSTXCuMjj3HupUGfOygQJwWN3Ta1fv2vkmVPpT+0D+Ht3zopA
P/039qgrMtQoIIUbVnHjykfb/bQmJWtB9VqDbBe/rWytaSpEiJvrD3NiRVLGpjHe
P5Cwg6ayBEWrZo+79BlmXcurZp3L2X6V+0SensAQFpKIpPa8k4lHLjsRzTq8lkta
2ORCvy9pmsWv91SmFXrcBv/mpSoZ8svbUvbJJulzmrVQUQE5s5BW7n46EbqmVqJR
Th3SkIQtwC0Hs945p25hgK80dBQSHqP6P4lrnrFo6TCbnLMcAdd0scPa9kJmrnvv
yHUmK8EffB5400i5AQ0ETTgBQQEIAPXiOZgblIz1wFuaxeaBGS3A37lFgpffm0Dl
jofMC/B1i4BSZHz0U5NO7O1KJ3afRSU74ffCUmANIM+O9SopA8zlW/clSig9IRJj
sYpi84OCsPT1kCMKpRARYChEPspitDeasrUmDQ3MbgH8vT0t2HWHEQdy4huGhBKm
stm4eV331i7AMbhy3zspZYVbfMz3qV3WVf8g1wGiNadCjBTl8sbzlW5IaJFFV+Fx
Ij6yzcco+1onHirxHm9Zdp/91hBZEiHbEAiGmKW6YIPvdLDITlFeRLf+X9D7/wpA
ebAqr0Ta4g2XXCdwqwS6bakTOftvUB4wAnh7jDFsF7diLMbc8C8AEQEAAYkBHwQY
AQIACQUCTTgBQQIbDAAKCRB8jv27OGchXSK4B/4pwSVL4fhJvwHh9eT40CD6D80D
3gg6l2BpYCs/pfvM+zfC0pP7YTZpTK+EXlC6SdralurYg4IgODQ1QijpG8j9jh09
Zb74SlLpZrrsB4jSXRrl/QHfFPdbZ7ONW8cRrNrrguCuVv6x0xCWkBzS+GyJKSUP
2uYxzWq8/eYHHOYXfzpG69VA1WUcKySQw3y5AIFxKxvVtV3NAkwG5tmbp2PArKR/
2V+36n9j2eu2eX7gKUCJGMRTCRaAxmCzRw84vMMT0Ty/wrFqLWDVukkrdFXVuIc4
NN/GEog89ee0x8W45XYoCZLP3CLnRnOXyMbvPwDcw++CLdAd/Sy/EsvjbSH6
=p+Vo
-END PGP PUBLIC KEY BLOCK-







Re: mvn clean package requests access rights for local Nexus repository

2015-03-19 Thread Stuart McCulloch
On Thursday, 19 March 2015 at 10:41, Markus Karg wrote:
 As I said I cannot reproduce the bug anymore, so do you think the requested 
 test makes any sense still?
  
  

The Nexus system feeds record authz/authc events as well as any upload attempts:

http://books.sonatype.com/nexus-book/reference/using-sect-feeds.html

this should help identify what exactly happened from the perspective of the 
server
  
 -Ursprüngliche Nachricht-
 Von: Martin Gainty [mailto:mgai...@hotmail.com]  
 Gesendet: Donnerstag, 19. März 2015 02:04
 An: users@maven.apache.org (mailto:users@maven.apache.org)
 Betreff: RE: AW: mvn clean package requests access rights for local Nexus 
 repository
  
 as bernd suggested can you view possible access when you enable -X?
 might also help to see extension errors with -e mvn -e -X package  
 package.out can we view package.out?
  
 I would be interested looking at the netstat deltas specifically
 shnetstat -a  netstat_before.log
 run command
 shmvn -X package
  
 run another shell and view any new network connections
  netstat -a  netstat_after.log
  
  
 any deltas between netstat_before.log and netstat_after.log can you display 
 both here so we can diff the 2 files?
 ?
 Martin
  
  
  From: k...@quipsy.de (mailto:k...@quipsy.de)
  To: users@maven.apache.org (mailto:users@maven.apache.org)
  Date: Wed, 18 Mar 2015 16:42:06 +0100
  Subject: AW: mvn clean package requests access rights for local  
  Nexus repository
   
  Bernd,
   
  your theory failed the test:
   
  * Unplugged USB stick, so Maven has no passwords anymore
  * Removed .m2\repository folder from disk, so Maven is enforced to  
  download rather everything newly from our Nexus mirror
  * mvn clean package built maven-dependency-plugin without any  
  problem
   
  Conclusion: It is definitively NOT a download problem, but still supports 
  my theory that maven-dependency-plugin wants to UPLOAD something at 
  package phase.
   
  If I just would have kept the protocol earlier today, I could tell you  
  what thing actually it was... :-(
   
  Regards
  -Markus
   
   
  -Ursprüngliche Nachricht-
  Von: Bernd [mailto:e...@zusammenkunft.net]
  Gesendet: Mittwoch, 18. März 2015 14:27
  An: Maven Users List
  Betreff: Re: mvn clean package requests access rights for local  
  Nexus repository
   
  Hello,
   
  It sounds more like a download as it does not ask again. You can wipe your 
  local repo cache (or use a different one in settings.xml) and try to 
  reproduce the problem. If you run with -X and actually keep the maven log 
  output you should be able to see the access in question.
   
  Gruss
  Bernd
  Am 18.03.2015 14:02 schrieb Markus Karg k...@quipsy.de 
  (mailto:k...@quipsy.de):
   
   Dear Maven Experts,

   just did svn checkout to get trunk of maven-dependency-plugin, and  
   wanted to build it using mvn clean package. What then happened is  
   really
   scary:


   * It complained about missing access on that path where my USB
   stick stores the encrypted password for my local Nexus repository.

   * My local Nexus repository is a mirror of central with public
   access, only demanding passwords for uploads.

   * I plugged in my stick, did mvn clean package again, and it
   worked pretty well.

   * REMOVED my stick, and since then mvn clean package works
   without, still!

   That looks if packaging maven-dependency-plugin would need to  
   WRITE into my Nexus (possibly central?) at package phase, if a  
   particular thing is not found there.

   This is scary, as nobody expects UPLOADS are done at packaging.

   If somebody has an explanation why that happens, I'd ask him to  
   publish here, so everybody will understand the reason for this! :)

   Regards
   -Markus

   
  B KKK
  KCB [ X ܚX KK[XZ[
   
  
 \ \ ][ X ܚX PX] [ \X K ܙ B ܈Y][
  ۘ[ [X[ K[XZ[
  
 \ \ Z[X] [ \X K ܙ B
  
  
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org 
 (mailto:users-unsubscr...@maven.apache.org)
 For additional commands, e-mail: users-h...@maven.apache.org 
 (mailto:users-h...@maven.apache.org)
  
  




Re: Minimum JDK for mojos

2015-03-19 Thread offbynull-maven
I understand that. But, shouldn't this be explicitly stated somewhere? 
Some official guide somewhere essentially saying that if you're planning 
on releasing your mojo publicly...


to support Maven2 you should be using JDK1.5 or lower (don't actually 
know if this is correct)

to support Maven3.0 to 3.2 you should be using JDK1.6 or lower
to support Maven3.3+ you should be using JDK1.7 or lower

On 3/19/2015 9:47 PM, Ron Wheeler wrote:

How else will it work?
If you compile it into Java 8 byte-code, the Java 6 run-time is going 
to have a tough time running it.


Ron
On 20/03/2015 12:31 AM, offbynull-maven wrote:
If the minimum JDK for Maven3 is JDK1.6, should my custom mojo always 
be built against JDK1.6 or lower?


Are there any guidelines around this?

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








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



Minimum JDK for mojos

2015-03-19 Thread offbynull-maven
If the minimum JDK for Maven3 is JDK1.6, should my custom mojo always be 
built against JDK1.6 or lower?


Are there any guidelines around this?

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



Re: Minimum JDK for mojos

2015-03-19 Thread Ron Wheeler

How else will it work?
If you compile it into Java 8 byte-code, the Java 6 run-time is going to 
have a tough time running it.


Ron
On 20/03/2015 12:31 AM, offbynull-maven wrote:
If the minimum JDK for Maven3 is JDK1.6, should my custom mojo always 
be built against JDK1.6 or lower?


Are there any guidelines around this?

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





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


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