A Danish company have been working on a Maven plugin for JMeter, and
are willing to contribute the code to either Maven or JMeter projects:
http://www.nabble.com/Contribution--tf4578005.html
Is this the sort of contribution that the Maven project would be interested in?
Although it is targeted
This started failing when the SVN repo was organised.
Please can someone update
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml
with the new location for the DOAP?
-- Forwarded message --
From: aps...@apache.org aps...@apache.org
Date: 13 Sep
On 26/02/2010, Brett Porter br...@apache.org wrote:
The Apache Maven team would like to announce the release of Maven 2.0.11.
http://maven.apache.org/download.html
This release is intended for all current users of Maven 2.0.10 and below who
are not able to upgrade to Maven 2.2.1, and
What is the recommended procedure for fixing hash files in a Maven
repo that have the wrong syntax?
For example:
file.tar.gz.sha1:
file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
3B4C
The hash is correct, but not all tools can process the hash when it
What is the recommended procedure for fixing hash files in a Maven
repo that have the wrong syntax?
For example:
file.tar.gz.sha1:
file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
3B4C
The hash is correct, but not all tools can process the hash when
On 26/04/2010, sebb seb...@gmail.com wrote:
What is the recommended procedure for fixing hash files in a Maven
repo that have the wrong syntax?
I have seen the reply about using Nexus, but if the project does not
use Nexus, what is the procedure?
If I update the hashes in the release repo
.
commons-compress-1.0-bin.tar.gz.md5:
commons-compress-1.0-bin.tar.gz: F8 F0 2E 1E AC 08 37 7D 75 14 CB 94 87 AF E2
C9
All the other hashes have the wrong syntax too.
On Wed, Apr 28, 2010 at 10:12 PM, sebb seb...@gmail.com wrote:
On 26/04/2010, sebb seb
On 28/04/2010, Juven Xu ju...@sonatype.com wrote:
On Wed, Apr 28, 2010 at 11:05 PM, sebb seb...@gmail.com wrote:
On 28/04/2010, Juven Xu ju...@sonatype.com wrote:
you can use these shell scripts:
find . -type f | xargs -i sh -c 'sha1sum {} | cut -d -f1 {}.sha1'
find
OK thanks very much.
If this problem recurs with other projects, is there a formal means of
reporting it?
e.g. via an issue tracker?
On 29/04/2010, Juven Xu ju...@sonatype.com wrote:
checksums on pgp signautes are deleted.
On Wed, Apr 28, 2010 at 11:34 PM, sebb seb...@gmail.com wrote
tasks here:
http://jira.codehaus.org/browse/MAVENUPLOAD
or at Sonatype:
https://issues.sonatype.org/browse/OSSRH
On Thu, Apr 29, 2010 at 4:12 PM, sebb seb...@gmail.com wrote:
OK thanks very much.
If this problem recurs with other projects, is there a formal means
Maybe someone should let her colleagues in on the fun that can be had
from OoO autoreplies ;-)
I wonder if the company realises how much internal information is
being allowed to leak out in OoO autoreplies...
On 30/04/2010, John Casey jdca...@commonjava.org wrote:
nice!
On 4/30/10 3:33 PM,
On 03/05/2010, Brett Porter br...@apache.org wrote:
On 01/05/2010, at 3:19 AM, Benjamin Bentmann wrote:
Hi,
considering the recent fixes to checksums for stuff in central, I was
wondering what's the overall state of (existing) checksums on central these
days?
Probably still not
The Apache parent pom version 7 seems to require Java 1.5 (because
maven-remote-resources-plugin v1.1 requires Java 1.5) yet the
compile.source and compile.target are 1.4.
Is it intentional that AP Pom v7 requires 1.5?
It would help if the Apache Parent Pom stated the minimum version of
Java it
On 11/06/2010, Kristian Rosenvold kristian.rosenv...@gmail.com wrote:
I have a memoizer
(http://www.javaconcurrencyinpractice.com/listings/Memoizer.java) that
I'd like to include somewhere in our code base. It's like 30 lines of
code or so.
Ï've seen this snippet of code (or extremely
On 11/06/2010, Brett Porter br...@apache.org wrote:
On 11/06/2010, at 4:27 PM, Kristian Rosenvold wrote:
I have a memoizer
(http://www.javaconcurrencyinpractice.com/listings/Memoizer.java) that
I'd like to include somewhere in our code base. It's like 30 lines of
code or so.
set of tools for
validation using humans, Black Duck and Palimida. If you've found a public
domain license
then you're fine, but I'll ask the Eclipse IP team.
Sebb identified the piece of code as public domain via the official
website of the book; I was looking in the hardcopy
On 20/05/2010, Marshall Schor m...@schor.com wrote:
Hi,
I've posted earlier on u...@maven.apache.org about a couple of possible
improvements to the
Apache Common Parent POM - used by Apache projects [1].
I'd like to add some Jira issues for these, but I was unable to determine
what
Have you seen this?
http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-IsJuliaAntonova/Tumlareoutoftheoffice?
But I agree it's annoying.
The problem is that there are lots of different ways of denoting OoO
messages. Just matching on subject line will result in false
positives.
I think
Why has SUREFIRE-536 still not been fixed?
It was originally reported against 2.4.3
On 16 August 2010 15:19, Stephen Connolly steph...@apache.org wrote:
The Maven team is pleased to announce the release of Surefire, version 2.6
This release includes the maven-surefire-plugin, which executes
On 16 August 2010 16:00, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Does the issue have a patch?
It does now.
Many thanks to Stevo Slavic.
Does the patch include integration tests that cover positive and
negative testing?
AFAIK.
Is the patch against the latest code base?
In which case please add some comments:
- to say why URL must be www.a.o
- to note the URL for the POM itself so people can find its documentation.
On 9 February 2011 02:27, Brian Fox bri...@infinity.nu wrote:
You realize that this may cause everyone to inherit the wrong url now?
We should have
I think this was my suggestion originally, as being one way to
document how to find information on the ASF POM from the POM.
I suggested using the url and issueManagement which provide the
relevant information.
However, a block comment would do just as well if those are needed to
be set
There are two useful fixes since 1.1, and only one outstanding bug.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
The assembly plugin is broken for versions after 2.2-beta-5.
Both 2.2 and 2.2.1 ignore attached assemblies which are defined in the
parent pom when running mvn install.
However the attached assemblies are processed if one runs mvn clean
install or mvn package install, and they are also processed
, that
are just lying around in file form in the target/ directory?
Is there a project out there I can take a look at that will exhibit the
problem?
See MASSEMBLY-553 for all the details.
On 4/14/11 9:20 AM, sebb wrote:
The assembly plugin is broken for versions after 2.2-beta-5.
Both 2.2 and 2.2.1
On 14 April 2011 16:47, John Casey jdca...@commonjava.org wrote:
On 4/14/11 11:37 AM, sebb wrote:
On 14 April 2011 15:26, John Caseyjdca...@commonjava.org wrote:
mvn package install == mvn install
Except that it behaves differently, which is why I think it may be
something more than
On 25 May 2011 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
These were Nicolas' tests, but a good catch and I've made the change.
BTW, the aim here is to reproduce the bugs for the first go... so if
Plexus Utils is incorrectly using platform encoding then actually the
test
On 26 May 2011 15:03, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
On 26 May 2011 12:57, sebb seb...@gmail.com wrote:
On 25 May 2011 10:04, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
These were Nicolas' tests, but a good catch and I've made the change.
BTW
On 1 June 2011 14:46, Brett Porter br...@apache.org wrote:
On 01/06/2011, at 8:21 PM, Stephen Connolly wrote:
REQUEST FOR COMMENTS: Potential migration of Maven's JIRA from
jira.codehaus.org to issues.apache.org
Just wondering now that codehaus and apache are on nearly similar
versions
Does Codehaus JIRA support adding SVN commit messages to issues?
I've yet to see any such entries, but in the ASF JIRA this is used extensively.
IMO it's a very useful feature - makes it much easier to follow what
happened to an issue later on.
I don't know whether the feature is not available,
On 4 June 2011 21:04, Dennis Lundberg denn...@apache.org wrote:
...
2. Please use the following form for the commit messages:
[issueId] issueSummary
for example:
[MCHANGES-254] Example doesn't work - spaces not allowed in statusIds
and resolutionIds after a comma
+1
It would be useful
to update :)
Unfortunately, it looks like Codehaus JIRA is not set up to add SVN
log messages to issue comments, so the SVN ids need to be added
manually to the issues.
--benson
On Sat, Jun 4, 2011 at 4:33 PM, Dennis Lundberg denn...@apache.org wrote:
On 2011-06-04 22:16, sebb wrote:
On 4 June
/repository/maven
We can discuss with Ben to see if we can fix it.
On Sun, Jun 5, 2011 at 1:48 AM, Benson Margulies bimargul...@gmail.comwrote:
I have been. Did I miss one?
This is generally a job for fisheye, after all.
On Sat, Jun 4, 2011 at 7:45 PM, sebb seb...@gmail.com wrote:
On 4
Thanks!
On 5 June 2011 17:15, Benson Margulies bimargul...@gmail.com wrote:
I've pasted all the checkin comments from my activities this weekend
into their respective jira.
-
To unsubscribe, e-mail:
On 6 June 2011 09:23, Dennis Lundberg denn...@apache.org wrote:
On 2011-06-05 01:45, sebb wrote:
On 4 June 2011 22:02, Dennis Lundberg denn...@apache.org wrote:
On 2011-06-04 22:44, Benson Margulies wrote:
Dennis,
Points taken. The web page with developer guidance does specifically
give
On 19 June 2011 11:52, Dennis Lundberg denn...@apache.org wrote:
On 2011-06-19 00:30, Benson Margulies wrote:
I just looked at the 'blocker' issues. We have a variety of very old
JIRAs here. None of the ones I looked at have a self-contained test
case that would can be downloaded, run, and
May I make a plea for the ASF POM to include a link to the
documentation in the comments?
Also, maybe someone can fix the very long comment line starting with:
As of Version 6,
The description could be wrapped as well.
On 27 June 2011 21:42, Benson Margulies bimargul...@gmail.com wrote:
It
On 28 June 2011 15:40, Benson Margulies bimargul...@gmail.com wrote:
Sebb,
I think that you are pointing at the dilemma at the center of this.
Anything like this that we put into the top pom is inherited unless
overriden, and people are skittish about accidently making everything
part
Looked around; cannot find out where to report bugs in the apache jar
resource bundle.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
On 17 December 2011 01:46, Stephen Connolly steph...@apache.org wrote:
The Maven team is pleased to announce the release of the Maven XXX
Plugin, version Y.Z
X, Y Z?
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in
On 12 February 2012 16:33, Dennis Lundberg denn...@apache.org wrote:
The Maven team is pleased to announce the release of the Maven Checkstyle
Plugin, version 2.9
Generates a report on violations of code style and optionally fails the build
if violations are detected.
The DIST directory currently contains the following Maven directories:
drwxrwsr-x 7 svnwc svnwc 8 Sep 20 10:59 maven
drwxrwsr-x 4 apbackup maven 5 Sep 1 17:32 maven_pre_svnpubsub
Is the maven_pre_svnpubsub directory still needed?
Is it referenced in any download pages?
On 28 December 2012 01:24, Kristian Rosenvold krosenv...@apache.org wrote:
The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.13
This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the
I expect you have all see the news about the Javadoc javascript bug.
It's going to take a long time for everyone to update their Java
installations to Java 1.7 u25. Likewise for builds that need to use
other Java versions, tweaking poms so Java 7 is used for Javadocs
whilst still maintaining
/JavadocUpdaterTool/blob/master/src/main/java/JavadocFixTool.java
That looks exactly like the file that was released by Oracle; anyone
can pick up the tool packaged as a jar from the Oracle web-site.
On it's own, it does not help.
Cheers
2013/6/19 sebb seb...@gmail.com
I expect you have all
lots of goals that occur in different
phases; the only way to be sure to fix all the issues is to always run
the tool after running Javadoc.
2013/6/20 sebb seb...@gmail.com:
On 19 June 2013 22:40, Baptiste MATHUS bmat...@batmat.net wrote:
Hi,
I think the best way to track this is to file a JIRA
On 20 June 2013 13:08, sebb seb...@gmail.com wrote:
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
JavadocFixTool.java in javadoc plugin
On 20 June 2013 13:21, Olivier Lamy ol...@apache.org wrote:
2013/6/20 sebb seb...@gmail.com:
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source
2013/6/20 sebb seb...@gmail.com
On 20 June 2013 13:21, Olivier Lamy ol...@apache.org wrote:
2013/6/20 sebb seb...@gmail.com:
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know
https://issues.apache.org/jira/browse/LEGAL-171
On 20 June 2013 15:35, Stuart McCulloch mccu...@gmail.com wrote:
On 20 Jun 2013, at 15:19, sebb wrote:
On 20 June 2013 14:20, Baptiste MATHUS bmat...@batmat.net wrote:
I'm +1 with you on the fact that this code should be included after each
On 21 June 2013 04:00, Steve Goodwin sgood...@cfl.rr.com wrote:
Hi,
I am simply trying to create a .zip from some folders in an svn project.
When I try to run this a maven build I get the following error:
That's really a question for the Maven Users list.
There are more subscribers to
I've just been told about the Maven Sandbox, which seems like it might
be a better location for two general purpose plugins that are
currently being developed at Apache Commons.
Digest
The digest plugin is a simple plugin that can generate hashes
(currently just MD5 and SHA1) for any files
On 23 June 2013 01:00, Olivier Lamy ol...@apache.org wrote:
2013/6/23 sebb seb...@gmail.com:
Also, is there a Sandbox repo where the plugins can be deployed for testing?
Or is it up to users to checkout the source and install the plugins locally?
We can deploy snapshots to repository.a.o
OK
On 24 June 2013 13:04, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Apache Maven Javadoc Plugin 2.9.1.
This version contains the code to fix the javadoc security issue after
the javadoc generation.
We fixed 6 issues:
On 24 June 2013 23:58, Olivier Lamy ol...@apache.org wrote:
2013/6/25 sebb seb...@gmail.com:
On 24 June 2013 13:04, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Apache Maven Javadoc Plugin 2.9.1.
This version contains the code to fix the javadoc security issue after
On 25 June 2013 00:26, ol...@apache.org wrote:
Author: olamy
Date: Mon Jun 24 23:26:16 2013
New Revision: 1496295
URL: http://svn.apache.org/r1496295
Log:
fix name
Modified:
maven/plugins/trunk/maven-javadoc-plugin/pom.xml
Modified: maven/plugins/trunk/maven-javadoc-plugin/pom.xml
On 25 June 2013 02:48, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Apache Maven Javadoc Plugin 2.9.1.
This version contains the code to fix the javadoc security issue after
the javadoc generation.
Since previous try I fix the @since for applying the javadoc security fix.
some expected
differences - e.g. DEPENDENCIES is only in the source archive
+1 on the release however it is odd that the Release Notes page is empty.
Please fix that on the actual site deploy.
Ralph
On Jun 24, 2013, at 7:15 PM, sebb wrote:
On 25 June 2013 02:48, Olivier Lamy ol...@apache.org
I'd like to try deploying a snapshot of the new digest plugin but I
get access denied errors.
Any idea why that should be?
I can deploy Common snapshots OK to the same repo; is there an ACL
that only allows Maven committers to deploy snapshots. or is some
other config needed?
On 25 June 2013 11:49, Olivier Lamy ol...@apache.org wrote:
2013/6/25 sebb seb...@gmail.com:
I'd like to try deploying a snapshot of the new digest plugin but I
get access denied errors.
Any idea why that should be?
IMHO you need to be in the maven group.
OK, NP.
I can deploy Common
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC.
The review process needs to establish that the proposed source release
meets those aims.
It's
that I am
reviewing the release contents.
Ralph
On Jun 25, 2013, at 9:52 AM, sebb wrote:
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC
the release contents.
Ralph
On Jun 25, 2013, at 9:52 AM, sebb wrote:
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC.
The review process
On 25 June 2013 19:33, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le mardi 25 juin 2013 17:52:20 sebb a écrit :
And it's not unknown for spurious files to creep into a release
(perhaps from a stale workspace - are releases always built from a
fresh checkout of the tag?)
we use the release
Most plugins seem to be sub-packages of org.apache.maven.plugin; just
a few use org.apache.maven.plugins (e.g. enforcer, shade).
Is there a convention as to which to choose, or are the plugins that
use plugins an anomaly?
-
To
On 26 June 2013 01:04, Chris Graham chrisgw...@gmail.com wrote:
-1
Except then the poms will point to the wrong place.
Depends how the poms are updated.
On Wed, Jun 26, 2013 at 10:01 AM, Gary Gregory garydgreg...@gmail.comwrote:
On Tue, Jun 25, 2013 at 7:14 PM, sebb seb...@gmail.com wrote
On 26 June 2013 00:34, Chris Graham chrisgw...@gmail.com wrote:
This appears to be a variant of the Do we reuse version numbers?
discussion of recent times.
That was resolved.
Can we please not rehash this?
-Chris
On Wed, Jun 26, 2013 at 2:52 AM, sebb seb...@gmail.com wrote:
The mission
I could not find any download links for Maven source packages.
As the ASF primary purpose is to release source, and that must be
released via the mirror system, there ought to be download pages with
links to the source package, sigs, hashes and KEYS file.
Yes, there are source packages for some
On 26 June 2013 01:13, Olivier Lamy ol...@apache.org wrote:
For historical reason this has changed etc..
Use org.apache.maven.plugins (same as groupId)
OK thanks, I'll stick with plugins for the new ones then.
2013/6/26 sebb seb...@gmail.com:
Most plugins seem to be sub-packages
On 26 June 2013 01:25, Barrie Treloar baerr...@gmail.com wrote:
And if the mvn deploy fails for any reason?
We get this often enough with a crappy connection to our nexus servers.
Is it necessary to re-run release:perform?
release:perform may be at the stage where it has deleted the
On 25 June 2013 20:15, Uwe Schindler u...@thetaphi.de wrote:
Hi,
I agree with sebb. I am not a Maven committer, but the release revision is
very important in the Lucene Project (where I am the chair).
We have another workflow, working with revision number:
- Release manager produces source
On 26 June 2013 01:43, Chris Graham chrisgw...@gmail.com wrote:
On Wed, Jun 26, 2013 at 10:36 AM, sebb seb...@gmail.com wrote:
However there is also the possibility that vital files are missing
from the source archive.
For that to be detected, a comparison with the SVN tag is needed.
How
On 26 June 2013 01:41, Olivier Lamy ol...@apache.org wrote:
correct.
In case of failure during deploy:
* cd target/checkout mvn clean deploy -Papache-release
or
* export/checkout the tag mvn clean deploy -Papache-release
Neither of those guarantee that the workspace agrees with the tag.
On 26 June 2013 02:14, Barrie Treloar baerr...@gmail.com wrote:
On 26 June 2013 09:47, sebb seb...@gmail.com wrote:
I could not find any download links for Maven source packages.
As the ASF primary purpose is to release source, and that must be
released via the mirror system, there ought
On 26 June 2013 02:18, Barrie Treloar baerr...@gmail.com wrote:
On 26 June 2013 10:19, sebb seb...@gmail.com wrote:
On 26 June 2013 01:41, Olivier Lamy ol...@apache.org wrote:
correct.
In case of failure during deploy:
* cd target/checkout mvn clean deploy -Papache-release
or
* export
herve.bout...@free.fr wrote:
the jar content isn't updated: so you have jar artifacts inconsistent with svn
Le mercredi 26 juin 2013 01:08:59 sebb a écrit :
On 26 June 2013 01:04, Chris Graham chrisgw...@gmail.com wrote:
-1
Except then the poms will point to the wrong place.
Depends how
On 26 June 2013 02:48, Barrie Treloar baerr...@gmail.com wrote:
On 26 June 2013 10:48, sebb seb...@gmail.com wrote:
The point is that the ASF release source, and it must be provided for
download via the ASF mirrors.
See:
http://www.apache.org/dev/release.html#host-GA
If you don't point
On 26 June 2013 02:59, Barrie Treloar baerr...@gmail.com wrote:
Then replace
cd target/checkout mvn clean deploy -Papache-release
with
delete target/checkout
svn co blah to target/checkout
mvn clean deploy -Papache-release
Since it was mvn release:perform that created target/checkout in
On 26 June 2013 10:56, Chris Graham chrisgw...@gmail.com wrote:
On Wed, Jun 26, 2013 at 7:06 PM, sebb seb...@gmail.com wrote:
I meant: if the pom is created with the correct final URLs in the
first place, it won't have to be changed.
They are. If you'd used the release plugin, then you
On 26 June 2013 23:54, ol...@apache.org wrote:
Author: olamy
Date: Wed Jun 26 22:54:24 2013
New Revision: 1497151
URL: http://svn.apache.org/r1497151
Log:
add a link to sources to get a bit of peace (I hope at least for few days :-))
-1
wrong URL.
Modified:
the tag
to rename it to e.g. maven-javadoc-plugin-2.9-rc1 using svn mv.
By means of this you are able to easily diff between e.g. released 2.8 and
the final 2.9 as well as between 2.9-rc1 and the final 2.9.
Regards Mirko
--
Sent from my mobile
On Jun 26, 2013 12:14 PM, sebb seb
On 25 June 2013 21:23, Robert Scholte rfscho...@apache.org wrote:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=19011
There are still a couple of issues left in JIRA:
to select the
revelant portion of the tree. The tag name is one such way to provide
the information.
Ralph
On Jun 25, 2013, at 4:14 PM, sebb seb...@gmail.com wrote:
It would be a lot better to use RC1 RC2 etc initially, and copy the
successful tag to the GA tag.
On 25 June 2013 19:38, Ralph Goers
On 25 June 2013 12:20, Fred Cooke fred.co...@gmail.com wrote:
Absolutely, sebb! This is what I've been saying all along. If I had more
time I'd vote -1 to every attempted release that used or intended to use
respun tags/artifacts without revisions and checksums. So here's one for
this one
The file
http://www.apache.org/dist/maven/KEYS
has two entries for F0E309FF - Vincent Massol
One of them should be deleted.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
from my mobile
On Jun 27, 2013 4:42 PM, sebb seb...@gmail.com wrote:
On 27 June 2013 15:05, Ralph Goers rgo...@apache.org wrote:
I do not believe that can be done with the release plugins as the pom
has to specify the same version as the tag. If you then rename the
tag you
would have
On 29 June 2013 11:47, Robert Scholte rfscho...@apache.org wrote:
Hi Sebb,
none of these files will end up in Maven Central, they are all used for
tests.
However, they do end up in the source release which is published via
the ASF mirrors.
It's vital that all released source files have
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC.
The review process needs to establish that the proposed source release
meets those aims.
It's
On 30 June 2013 20:00, Jason van Zyl ja...@tesla.io wrote:
Here are the release bits for 3.1.0:
Release notes:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967
Staging repository:
https://repository.apache.org/content/repositories/maven-084/
Staged
On 30 June 2013 20:55, Robert Scholte rfscho...@apache.org wrote:
The Apache Maven team is pleased to announce the release of the Maven
Enforcer Plugin, version 1.3
The Enforcer plugin provides goals to control certain environmental
constraints such as Maven version, JDK version and OS family
On 30 June 2013 21:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
On Sunday, 30 June 2013, sebb wrote:
On 29 June 2013 11:47, Robert Scholte rfscho...@apache.org javascript:;
wrote:
Hi Sebb,
none of these files will end up in Maven Central, they are all used for
tests
provenance otherwise.
Fred.
On Sun, Jun 30, 2013 at 8:20 PM, sebb seb...@gmail.com wrote:
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC
On 30 June 2013 21:25, rfscho...@apache.org wrote:
Author: rfscholte
Date: Sun Jun 30 20:25:21 2013
New Revision: 2333
Log:
Store all required release files of every available enforcer version
Added:
release/maven/enforcer/
Surely enforcer should be under release/maven/plugins?
Or
On 30 June 2013 21:56, Fred Cooke fred.co...@gmail.com wrote:
OK, so what is the Git command to download a copy of the sources that
are part of the hash?
git checkout hash
Does not work for me.
I get the following error message:
fatal: Not a git repository (or any of the parent
by
- the distinction is important.
Furthermore, the NOTICE file refers to additonal 3rd party software,
but there don't appear to be any LICENSE files for the software.
The licenses should either be in LICENSE.txt or linked therefrom.
-1 (non-binding)
On 30 June 2013 20:43, sebb seb...@gmail.com
22:35:40 +0200 schreef sebb seb...@gmail.com:
On 30 June 2013 21:25, rfscho...@apache.org wrote:
Author: rfscholte
Date: Sun Jun 30 20:25:21 2013
New Revision: 2333
Log:
Store all required release files of every available enforcer version
Added:
release/maven/enforcer/
Surely
On 30 June 2013 23:28, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
On Sunday, 30 June 2013, sebb wrote:
On 30 June 2013 21:56, Fred Cooke fred.co...@gmail.com javascript:;
wrote:
OK, so what is the Git command to download a copy of the sources that
are part of the hash
On 30 June 2013 19:20, sebb seb...@gmail.com wrote:
The mission of the ASF is to release software as source, and to ensure
that the released source is available under the Apache Licence.
Before a release can be approved it must be voted on by the PMC.
The review process needs to establish
On 30 June 2013 23:32, Benson Margulies bimargul...@gmail.com wrote:
On the one hand, I think that, in many Apache communities, comparing the
source release to the VCS is the exception and not the rule, and may never
have happened, even once. (I think that there is at least an even chance
that
On 1 July 2013 03:56, Barrie Treloar baerr...@gmail.com wrote:
On 1 July 2013 06:52, sebb seb...@gmail.com wrote:
Another problem: the NOTICE file contains the following spurious text:
=
== NOTICE file
1 - 100 of 233 matches
Mail list logo
