On 25 December 2016 at 04:15, Bernd Eckenfels wrote:
> Hello Ralph, besides the strange .pgp.asc files (and I think some components
> don't have that problem) the component releases should not need to actually
> delete artifacts in the staged repo when running the documented release
> goal/prof
Hello Ralph, besides the strange .pgp.asc files (and I think some components
don't have that problem) the component releases should not need to actually
delete artifacts in the staged repo when running the documented release
goal/profile.
You can in the POM control what is attached for some plug
Maven is going to publish all the artifacts that are built to the repository.
This isn’t necessarily a bad thing as people can look at them all in one place
during the vote. But after the vote is approved anything that a user wouldn’t
ever want in a maven build should be deleted before the rele
I tested IDEs with a non-standard packaging of -sources.jar; java sources were
inside of src/main/java/ folder.
- Eclipse was able to use.
- IntelliJ was able to use with a few extra clicks.
- Netbeans was NOT able to use.
I don’t think this option should be pursued further.
A better alternative
Gary Gregory wrote:
> On Fri, Dec 23, 2016 at 1:06 PM, Bernd Eckenfels
[snip]
>> Can you name a component where this is true? Afaik all Commons
>> components have a full featured source archive which is buildable and a
>> limited source attachment for maven.
>>
>
> That true, the whole point o
Hi Charles,
Charles Honton wrote:
> I am incorrect about the contents of the sources zip. It does contain
> all the files under source control.
>
> As a test, I replaced
> ~/.m2/repository/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5-
src.jar
??
The default release profile of Maven
On Fri, Dec 23, 2016 at 4:02 PM, Charles Honton wrote:
>
> I am incorrect about the contents of the sources zip. It does contain
> all the files under source control.
>
> As a test, I replaced ~/.m2/repository/org/apache/
> commons/commons-lang3/3.5/commons-lang3-3.5-src.jar with the distributi
I am incorrect about the contents of the sources zip. It does contain all the
files under source control.
As a test, I replaced
~/.m2/repository/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5-src.jar
with the distribution commons-lang3-3.5-src.zip. Using the eclipse IDE, I
navigate
I would think we would want a release paradigm that is as similar to as many
other projects as possible, for the sake of intuitive navigation of the project
from the consumer perspective.
Might we look at some other large (Apache v. non-Apache and java v. non-java)
projects to see how we stack
Hello,
I think hybrid -sry/source does not work very well, since the IDE expect a
package-like directory structure. I am not sure it would work with src/main/
prefix.
Gruss
Bernd
--
http://bernd.eckenfels.net
On Fri, Dec 23, 2016 at 11:33 PM +0100, "Gary Gregory"
wrote:
On Fri,
On Fri, Dec 23, 2016 at 12:54 PM, Charles Honton wrote:
> Several recent email threads have discussed our parent pom and release
> process. The process we have derive from Apache Common’s rich history
> which pre-dates many current distribution practices. I’d like to summarize
> several quirks
On Fri, Dec 23, 2016 at 1:06 PM, Bernd Eckenfels
wrote:
> Am Fri, 23 Dec 2016 12:54:14 -0800
> schrieb Charles Honton :
>
> > The
> > official release source tarball contains just the sources, not all
> > the project files. Building the artifact from just the src directory
> > without the pom wo
Am Fri, 23 Dec 2016 12:54:14 -0800
schrieb Charles Honton :
> The
> official release source tarball contains just the sources, not all
> the project files. Building the artifact from just the src directory
> without the pom would be extremely difficult.
Can you name a component where this is tru
Several recent email threads have discussed our parent pom and release process.
The process we have derive from Apache Common’s rich history which pre-dates
many current distribution practices. I’d like to summarize several quirks with
our current releases:
The official release source tarball
14 matches
Mail list logo
