Thanks,
So currently we deploy to OSSRH?
I'll let the central support staff know that, so that they can at
least prohibit plexus deploys to nexus.codehaus.org.
On Tue, Mar 10, 2015 at 11:45 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I asked Brian if there was any way to get
The Apache Maven team is pleased to announce the release of the
Apache Maven Patch Plugin, version 1.2
The Patch Plugin is used to apply patches to source files.
http://maven.apache.org/plugins/maven-patch-plugin/
plugin
groupIdorg.apache.maven.plugins/groupId
The Apache Maven team is pleased to announce the release of the
Apache Maven Jar Plugin, version 2.6
This plugin provides the capability to build jars.
http://maven.apache.org/plugins/maven-jar-plugin/
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
I asked Brian if there was any way to get central publishing rights linked
to github org membership, much like what we might want for mojo. I did not
get any specific reply, maybe he'll read this :)
Kristian
2015-03-09 23:33 GMT+01:00 Olivier Lamy ol...@apache.org:
AFAIK we have switched
Hello Maven folks,
I wonder if there is a possibility to include release notes for plugin versions
into the common maven site structure. the release notes are available via
announcement email (i.e. attached mail) or via JIRA issue tracker from i.e.
Hi Stephan,
the question on this is: What would be the benefit of this? Or in other
words: Will it bring supplemental information?
All the information is available as you already mentioned...if you
really interested you can find the information
Apart from that i could think of using
Hi Robert Kristian,
Early Access build for JDK 9 b53 https://jdk9.java.net/download/
available on java.net, summary of changes are listed here
http://www.java.net/download/jdk9/changes/jdk9-b53.html
Early Access build for JDK 8u60 b05 http://jdk8.java.net/download.html
is available on
This is a bit of a can of worms, but release notes (=jira issues) may very
well change after the release. This is a particular problem with deeply
componentized architectures like maven itself, issues fixed somewhere in
the bowels of the dependency hierarchy may turn out to have value that is
2015-03-08 16:07 GMT+01:00 Tibor Digana tibordig...@apache.org:
As you said, the SPI did not work well in multimodule project.
You tested SPI in Maven, so you know better than me :)
The problem is really only once the SPI project is in the same reactor as
is using it. Even then there were
I agree that there is no HUGE benefit to it. Just a matter of conformity to
common practices.
When you start to release will the release notes from the JIRA version be
finished? That way one could append the link of the release notes to the
project overview page before the maven site
I agree, publishing a static release notes makes it hard to add in Known
Issues as they are discovered, plus you want to know all the bugs that have
been found in a specific versions also.
Now of course there is the question of who maintains the known issues,
etc... and I agree that we may not be
The current plan is to continue running nexus.codehaus.org and then
move stuff over to ossrh as needed. The ssl cert was just renewed and
Bob said the DNS isn't going away immediately. We figure projects have
enough other stuff to scurry around changing, Nexus doesn't have to be
part of it at the
Hervé,
After EclipseCon today I will look at the doco you started (much appreciated)
and fill in some information. I'll try once again to get the release staged as
well.
Do you think you can put the site plugin along with related plugins through
it's paces with master to make sure we didn't
Github user ifedorenko commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78070683
http://jira.codehaus.org/browse/MNG-5783 should be fixed in master now.
I've provided explanation of the problem and links to the fix and corresponding
IT changes in
HI Brian,
Thanks for the input, but now I'm confused.
The POMs for plexus currently points to OSSRH. Can anyone who has done
a release of a plexus component lately shed some light on where they
go? Either nexus.codehaus.org och OSSRH.
On Tue, Mar 10, 2015 at 6:28 PM, Brian Fox
In the last two releases of surefire, we included the jira-report in the
site, listing all resolved issues with the appropriate fix-version:
http://maven.apache.org/surefire/maven-surefire-plugin/jira-report.html
Am Dienstag, 10. März 2015 schrieb Karl Heinz Marbaise :
Hi Stephan,
On
Java 7, ie 3.2(Java 6)/3.3(Java 7+current changes)
or
Java 6, ie 3.2(Java 6)/3.3(Java 6+current changes)/3.4(Java 7, ~1 month later)
?
Regards,
Hervé
Le lundi 9 mars 2015 09:35:30 Jason van Zyl a écrit :
Yes, I'll leave it until Wednesday to see if anyone has any issues running
master and
GitHub user arcivanov opened a pull request:
https://github.com/apache/maven/pull/39
[MNG-5688] mvn script is not compatible with OSX (Darwin)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arcivanov/maven MNG-5688
I think we're spending far too much energy on this discussion. Roll back to
1.6/1.6 and make the 3.4 1.7.
Kristian
2015-03-10 8:50 GMT+01:00 Hervé BOUTEMY herve.bout...@free.fr:
Java 7, ie 3.2(Java 6)/3.3(Java 7+current changes)
or
Java 6, ie 3.2(Java 6)/3.3(Java 6+current
Le jeudi 5 mars 2015 08:23:43 Hervé BOUTEMY a écrit :
Le mercredi 4 mars 2015 07:14:32 Jason van Zyl a écrit :
At this point we might as well just chat in the dev hangout tomorrow.
+1
Today
I'll focus on some more testing and documentation.
where is the documentation you're working
Perso, last time I deployed a plexus component it went to oss.sonatype.org.
As the pom says:
https://github.com/codehaus-plexus/plexus-pom/blob/master/pom.xml#L286
Olivier
On 11 March 2015 at 06:18, Dennis Lundberg denn...@apache.org wrote:
HI Brian,
Thanks for the input, but now I'm
Sorry, I was talking generically about projects using
nexus.codehaus.org not Plexus specifically. Since that's already using
ossrh, there are no implications.
On Tue, Mar 10, 2015 at 3:18 PM, Dennis Lundberg denn...@apache.org wrote:
HI Brian,
Thanks for the input, but now I'm confused.
The
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78013185
I chatted with Igor and he's going to try and change the way the classpath
is constructed for plugins. The issue here appears to be forking where SLF4J is
filtered out of
I agree we're spending too much energy but I don't plan to roll anything back.
I do not want to support the rather large feature set change across 1.6 and 1.7
because it will be a huge maintenance burden. It's entirely unrealistic to try
and support 1.6 and 1.7 given the activity in the core by
24 matches
Mail list logo
