Re: http://repository.apache.org/ is down?

Up here is Sourthern Cal. Gary On Sun, Jun 7, 2015 at 5:41 PM, Dan Tran wrote: > Can someone confirm if http://repository.apache.org is down at your side? > > Thanks > > -Dan > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: http://repository.apache.org/ is down?

It is back now in California Thanks -Dan On Sun, Jun 7, 2015 at 5:47 PM, Igor Fedorenko wrote: > Nexus UI showed up from here (Toronto). > > -- > Regards, > Igor > > On Sun, Jun 7, 2015, at 08:41 PM, Dan Tran wrote: > > Can someone confirm if http://repository.apache.org is down at your > side

Re: http://repository.apache.org/ is down?

Nexus UI showed up from here (Toronto). -- Regards, Igor On Sun, Jun 7, 2015, at 08:41 PM, Dan Tran wrote: > Can someone confirm if http://repository.apache.org is down at your side? > > Thanks > > -Dan - To unsubscribe, e-ma

http://repository.apache.org/ is down?

Can someone confirm if http://repository.apache.org is down at your side? Thanks -Dan

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

I see. In that case Kristian is right: it's a bug. Op Sun, 07 Jun 2015 19:33:03 +0200 schreef Karl Heinz Marbaise : Hi, i wasn't discussing what kind of entries / attributes whould be helpfull... In my current builds i have much more information in there like groupId, artifactId, versio

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

Hi, i wasn't discussing what kind of entries / attributes whould be helpfull... In my current builds i have much more information in there like groupId, artifactId, version, etc. This was more about ordering / adding supllemental entries if i have provided an MANIFEST.MF file...reusing it...

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

The sections should be preserved though, so that's definitely a bug. K 2015-06-07 19:17 GMT+02:00 Robert Scholte : > The following attributes are very handsome to be able to reproduce a build > based on sources > > Built-By: kama > Build-Jdk: 1.7.0_21 > Created-By: Apache Maven 3.1.1 > Archiver

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

The following attributes are very handsome to be able to reproduce a build based on sources Built-By: kama Build-Jdk: 1.7.0_21 Created-By: Apache Maven 3.1.1 Archiver-Version: Plexus Archiver I've hit several projects which I had to rebuild and this gave me enough info to do so. You actually

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

S; if you cannot add a class-path element to the manifest then ? You're wrong. Kristian 2015-06-07 19:09 GMT+02:00 Karl Heinz Marbaise : > Hi Igor, > > > On 6/7/15 6:57 PM, Igor Fedorenko wrote: > >> If I provide custom jar manifest, I expect the manifest to be used >> as-is, without anythi

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

Hi Igor, On 6/7/15 6:57 PM, Igor Fedorenko wrote: If I provide custom jar manifest, I expect the manifest to be used as-is, without anything added, removed or reordered. Just my 2 kopecks. That's exactly what i would expect...but in all our components / plugins it works different Abou

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

The jar specification says explicitly that "Attributes which are not understood are ignored."; I interpret this to mean it's ok for every man and his dog to add values. Which I think means that you should expect your *values* to win, not necessarily your particular file - there's an implicit suppor

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

Indeed, I would not expect to having my provided manifest modified at all. On 2015-06-07 18:57, Igor Fedorenko wrote: If I provide custom jar manifest, I expect the manifest to be used as-is, without anything added, removed or reordered. Just my 2 kopecks. ---

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

If I provide custom jar manifest, I expect the manifest to be used as-is, without anything added, removed or reordered. Just my 2 kopecks. -- Regards, Igor On Sun, Jun 7, 2015, at 12:50 PM, Karl Heinz Marbaise wrote: > On 6/7/15 6:49 PM, Karl Heinz Marbaise wrote: > > Sorry was too fast with my

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

On 6/7/15 6:49 PM, Karl Heinz Marbaise wrote: Sorry was too fast with my send button... Hi, at the moment i trying to dive into handling of MANIFEST.MF file [1], [2]... If i create a MANIFEST.MF my own and let maven-jar-plugin take that file via useDefaultManifest (target/classes/META-INF/MAN

MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

Sorry was too fast with my send button... Hi, at the moment i trying to dive into handling of MANIFEST.MF file [1], [2]... If i create a MANIFEST.MF my own and let maven-jar-plugin take that file via useDefaultManifest (target/classes/META-INF/MANIFEST.MF) it will be extended by several entr

MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

Hi, at the moment i trying to dive into handling of MANIFEST.MF file [1], [2]... If i create a MANIFEST.MF my own and let maven-jar-plugin take that file via useDefaultManifest (target/classes/META-INF/MANIFEST.MF) it will be extended by several entries: My own file: For example: Manifest

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4

Hi, On 6/7/15 12:15 PM, Karl Heinz Marbaise wrote: Hi, We solved 14 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20sta

Re: 3.0 versions in branches ?

I don't expect M2 specific changes on the shared component anymore, so I think we those projects are ready to be merged back to the trunk. That is: - maven-artifact-transfer - maven-common-artifact-filters - maven-dependency-tree Let me do that the following period, including the creation of ma

Re: 3.0 versions in branches ?

And I appreciate your work a lot. I've got the assembly-plugin migration in github and I'll just land that right on trunk once I'm happy with it. Kristian 2015-06-07 17:35 GMT+02:00 Robert Scholte : > Hi, > > I've made those branches to see how much work it is to drop M2 support and > to not lo

Re: 3.0 versions in branches ?

Hi, I've made those branches to see how much work it is to drop M2 support and to not lose my work. And it is quite a lot. I still haven't covered everything. I'm actually happy I didn't use the trunk for it, since now it was possible to do a 2.x release of the maven-shade-plugin. Now we'r

Re: 3.0 versions in branches ?

+1 On Sunday, June 7, 2015, Kristian Rosenvold wrote: > Do we really need to keep the 3.0 versions in branches ? Can't we just make > a branch if we need to fix something in the 2.x range ? > > Kristian > -- Sent from my phone

[GitHub] maven pull request: MNG-5837: Use a subshell, rather than the 'loc...

GitHub user josephw opened a pull request: https://github.com/apache/maven/pull/50 MNG-5837: Use a subshell, rather than the 'local' keyword, for POSIX compliance 'local' is not POSIX, but supported by most shells. However, it's not supported by Solaris's /bin/sh, so use a subsh

3.0 versions in branches ?

Do we really need to keep the 3.0 versions in branches ? Can't we just make a branch if we need to fix something in the 2.x range ? Kristian

[VOTE] Release Apache Maven Shade Plugin version 2.4

Hi, We solved 14 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priori