Links look better now. Thanks!
—jason
On July 28, 2018 at 2:05:02 AM, Karl Heinz Marbaise (khmarba...@gmx.de) wrote:
Hi Jason,
On 27/07/18 23:41, Jason Dillon wrote:
> On this page:
>
> https://maven.apache.org/mailing-lists.html
>
> It looks like the sub/unsub/
On this page:
https://maven.apache.org/mailing-lists.html
It looks like the sub/unsub/post links like:
https://maven.apache.org/users-subscr...@maven.apache.org
https://maven.apache.org/users-unsubscr...@maven.apache.org
https://maven.apache.org/us...@maven.apache.org
Are broken. These end
Yes please, thank you :-]
—jason
On May 24, 2017 at 2:38:24 PM, Igor Fedorenko (i...@ifedorenko.com) wrote:
I'd like to ask for somebody to second my change described in
[MNG-6233]. The change cleans up mixture of jsr330 and plexus
annotations used in maven-resolver-provider, leaving only
Folks, just a quick not that I’ve updated Maven Shell for the latest release,
can be found with the latest SNAPSHOT:
https://oss.sonatype.org/content/repositories/snapshots/com/planet57/maven/shell/dist/mvnsh-assembly/1.2.0-SNAPSHOT/
Locally seems to be fully functional. I’ve been updating
Okay, good luck. Let me know if you change your mind and need improvements to
gossip.
Cheers,
—jason
On October 22, 2016 at 10:20:08 AM, Hervé BOUTEMY (herve.bout...@free.fr) wrote:
thanks for sharing what you had, this really helped me work on the topic,
testing and learning misc
FTR I choose Gossip because it was an slf4j impl I created which had more
features than slf4j-simple but was also very small, and I had already
previously implemented a ANSI color rendering scheme for it, as it was used by
Maven Shell.
Its true that Gossip doesn’t have the same features as
Gossip presently doesn’t allow you to set adhoc logging configuration via
system properties, but as you have discovered uses a configurable
properties file to allow a profile to be configured to adjust your logging
as needed. I suppose that feature could be added, either to gossip proper
to as a
> And if folks really just want any use of green to become blue, then yes
> you can do that now and there is no reason to change anything further.
> Though I kinda doubt that is what folks want when then think about
> customization of colors. I expect folks really want more control over
>
On June 15, 2016 at 12:07:32 AM, Christian Schulte (c...@schulte.it) wrote:
Am 06/15/16 um 00:17 schrieb Jason Dillon:
> Making the colors configurable seems like a lot of overhead for what is
> otherwise fairly simple.
>
> I’d recommend leaving the colors asis for now, get thi
Making the colors configurable seems like a lot of overhead for what is
otherwise fairly simple.
I’d recommend leaving the colors asis for now, get this out to let users
actually make use of it, and then consider adding complexity later to make
colors configurable.
I don’t see a clean way to
colors for Linux are not exactly the same as the screen dump: yellow from the
screen dump is bold white on Linux. This is ok for me
Terminals can render whatever colors they want for the ANSI colors and many
have this configurable.
To be clear my terminal env has bold color rendering as yellow
If its on by default I would expect folks to set
MAVEN_OPTS=-Dmaven.logging=plain instead of magically making —batch do that.
If we mutate the cli api slightly to expose more details about the cli
configuration to the Slf4jConfiguration then regular -Dmaven.logging=plain on
command line would
On June 2, 2016 at 3:15:35 PM, Hervé BOUTEMY (herve.bout...@free.fr) wrote:
I merged the PR in the slf4j-gossip branch (and added a little improvement)
core ITs are ok (notice: ran without activating colors)
The testsuite certainly will not be very happy with color enabled as many tests
are
Jason, if you have a built version, do you mind adding it as a download to
the release files?
I can make a binary of this, though I do plan on fixing it up so that folks can
build it in the near future.
Build up here for the moment:
On March 8, 2016 at 7:45:53 AM, Jeff Jensen (jeffjen...@upstairstechnology.com)
wrote:
FYI Just cloned and tried build but Jansi 1.2 is not in Central: "Could not
find artifact org.fusesource.jansi:jansi:jar:1.2".
On March 3, 2016 at 5:42:56 AM, Tamás Cservenák (ta...@cservenak.net) wrote:
Maven Shell?
https://github.com/jdillon/mvnsh
Does anyone actually use this?
—jason
Any idea when this will get released?
11 issues fixed.
--jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
The github ribbon muck in maven-fluido-skin 1.2.2 covers the topBar.
… would actually like a bottom-right or something instead.
Is bottom locations on the roadmap, or at least updated skin to fix the zorder?
--jason
-
To
This would be slightly better if the titter button was floating in the topBar
with some padding around it… instead of sticking to the top.
--jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
The DefaultSecDispatcher defined in
https://github.com/apache/maven-3/blob/trunk/maven-core/src/main/resources/META-INF/plexus/components.xml
is missing a requirement:
requirement
roleorg.sonatype.plexus.components.sec.dispatcher.PasswordDecryptor/role
field-name_decryptors/field-name
Why don't you just fix the parsers in older mavens (ie. make a new release of
old-maven-version-x w/fixed parser) that allows for changes in newer versions?
Seems like if you can never add new information to the pom to solve
problems/add features in Maven 3 w/o completely breaking Maven 2, then
There are running up here no?
https://builds.apache.org/hudson/view/M-R/view/Maven/
--jason
On Apr 25, 2011, at 5:16 PM, Mark Derricutt wrote:
Hey all,
I see they maven nightly/ci build no longer seems to be on
https://grid.sonatype.org/ci - has it moved somewhere?
Mark
--
Great
I didn't see the take 2... make it so
+1
--jason
On Nov 4, 2010, at 10:52 AM, Brian Fox wrote:
noone wants an enforcer release?
On Tue, Nov 2, 2010 at 5:52 PM, Brian Fox bri...@infinity.nu wrote:
Hi,
Take 2, I added MENFORCER-109.
Changelog:
+1
--jason
On Nov 2, 2010, at 10:47 AM, Brian Fox wrote:
Hi,
Changelog:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=13616
Staging repo:
https://repository.apache.org/content/repositories/maven-009/
Staging site:
I upgraded to 1.11.22 a few hours ago and started a new build of maven-scm,
still failing some tests, but looking better:
https://grid.sonatype.org/ci/job/maven-scm/jdk=1.5,label=windows/128/
--jason
On May 16, 2010, at 12:37 AM, Olivier Lamy wrote:
ping !
2010/5/8 Olivier Lamy
Its the repo trigger that is barfing... it will soon be replaced. You can
ignore this error, it only means that Hudson will not be able to trigger the
build when a SNAPSHOT changed.
--jason
On May 6, 2010, at 10:44 PM, Barrie Treloar wrote:
There are errors but the build is marked as
http://maven.apache.org/plugins/ version needs to be updated.
--jason
On Feb 26, 2009, at 10:40 AM, Brian Fox wrote:
The Maven team is pleased to announce the release of the Maven
Enforcer Plugin, version 1.0-beta-1
The Enforcer plugin is used to fail a build if certain constraints are
not
http://maven.apache.org/plugins/ version needs to be updated.
--jason
On Feb 27, 2009, at 9:24 AM, John Casey wrote:
The Maven team is pleased to announce the release of version 2.5 of
Maven Plugin Tools, including the Maven Plugin Plugin.
These libraries are used to generate plugin
+1
--jason
On Feb 23, 2009, at 10:19 AM, Brian E. Fox wrote:
Time to release a beta with a few bug fixes:
Release Notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14948styleName
=HtmlprojectId=11530Create=Create
Staged site:
+1
--jason
On Jan 24, 2009, at 1:40 PM, Oleg Gusakov wrote:
I feel I owe an explanation about what was going with the release.
As we tried to refactor out jetty server code out of the transport
provider, we hit a few bumps on the road. But with the help from
Jetty community, who were
Have you published the artifacts to central? Its been 2 hours and I
still don't see them.
--jason
On Dec 12, 2008, at 1:02 PM, Oleg Gusakov wrote:
6 votes casted
[+1] 6: 4 binding, 2 non-binding
[-1]
[0]
I released Mercury 1.0.0-alpha-2, site at http://maven.apache.org/mercury
Thanks,
Oh, I thought it was the same sync'ing as with sites, every few hours,
or has that changed now too?
--jason
On Dec 12, 2008, at 3:05 PM, Brett Porter wrote:
The sync is only once a day. They are already at the apache rsync
repo.
- Brett
On 12/12/2008, at 7:01 PM, Jason Dillon wrote
+1
--jason
On Dec 8, 2008, at 2:18 PM, Oleg Gusakov
[EMAIL PROTECTED] wrote:
Dear All,
This is the first release of Mercury with all major [mercury]
functionality enabled: repository access + dependency resolution.
You can try using it for resolving artifacts and then writing them
Doesn't seem like it should have been rejected. Why are you posting
this to the maven list though?
--jason
On Oct 9, 2008, at 5:28 PM, nicolas de loof wrote:
Hi
I have asked to create a JIRA project for the Mojo GWT-maven-plugin,
before
I call for a vote and promotion from sandbox.
+1
Will this also include the non-transport bits? I'm looking to consume
those in gshell ASAP to replace maven-artifact.
--jason
On Oct 4, 2008, at 12:02 PM, Oleg Gusakov wrote:
I open this vote to release mercury 1.0.0-alpha-1 and promote it out
of sandbox, so that we can start using
+1
--jason
On Sep 23, 2008, at 2:14 AM, Raphaël Piéroni wrote:
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14253
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Beware of MNG-2974, a workaround is
+1
--jason
On Sep 17, 2008, at 8:53 AM, Dan Fabulich wrote:
This plugin can build a subset of interdependent projects in a
reactor. It should be useful in large reactor builds that include
irrelevant stuff you're not working on.
http://maven.apache.org/plugins/maven-reactor-plugin/
A
+1
--jason
On Sep 16, 2008, at 4:12 AM, John Casey wrote:
Hi everyone,
After fixing 70 issues and spending about 2 months going through
release candidate after release candidate, we finally have a stable
codebase!
To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The
Mix-ins would be wonderful IMO... :-)
--jason
On Sep 12, 2008, at 5:51 AM, Brian E. Fox wrote:
Alright, I'm pulling the trigger on this one and cancelling the
vote. I
have to monkey with the poms some more to line up the plugin with the
values in the maven-plugin-parent. This is a good
+1
--jason
On Sep 9, 2008, at 7:38 AM, Brian E. Fox wrote:
Time to release the enforcer with all its new rules.
The plugin is staged here:
http://people.apache.org/~brianf/stage/
The site is staged here:
http://people.apache.org/~brianf/plugins/maven-enforcer-plugin/
Folks a new snapshot of GMaven is out, this one mainly fixes problems
with Maven 2.1 usage, and IDE integration which uses the Maven 2.1
embedder.
Give it a whirl and report any issues, will release in a few days if I
don't hear of any problems. This should sort out the last of the
Its been a long time... still waiting for a release so I can use the
requirePluginVersions rule. What is holding it back from a release?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Thanks!
--jason
On Aug 29, 2008, at 7:39 PM, Brian E. Fox wrote:
My vacation, but I'll try to find time this weekend to get it done.
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Friday, August 29, 2008 3:56 AM
To: Maven Developers
Anyone?
--jason
On Thu, Aug 21, 2008 at 3:52 PM, Jason Dillon [EMAIL PROTECTED] wrote:
Seems that with svn 1.4.4 the maven-release-plugin works just fine... whats
going on with SVN 1.5.x?
--jason
On Aug 21, 2008, at 2:15 PM, Jason Dillon wrote:
I'm having lots of problems using
On Aug 20, 2008, at 11:35 AM, Jason van Zyl wrote:
Do your archetypes refer to repositories that you defined?
Not sure what you mean... :-\
--jason
On 19-Aug-08, at 8:36 PM, Jason Dillon wrote:
Hiya, I'm getting lots of user reports of problems using the GMaven
archetypes... could
a release 2.0-alpha4
soon
2008/8/20 Jason Dillon [EMAIL PROTECTED]:
Hiya, I'm getting lots of user reports of problems using the GMaven
archetypes... could be my fault for not really understanding how
the new
stuff works fully. But seems like folks that don't already have the
artifacts
I'm having lots of problems using the maven-release-plugin with SVN
1.5.x on my Mac. I found this thread:
http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html
Didn't find any solution though... except to use SVN 1.4.x, though
seems like I can't checkout with
Seems that with svn 1.4.4 the maven-release-plugin works just fine...
whats going on with SVN 1.5.x?
--jason
On Aug 21, 2008, at 2:15 PM, Jason Dillon wrote:
I'm having lots of problems using the maven-release-plugin with SVN
1.5.x on my Mac. I found this thread:
http
Hiya, I'm getting lots of user reports of problems using the GMaven
archetypes... could be my fault for not really understanding how the
new stuff works fully. But seems like folks that don't already have
the artifacts in their local repo (most users) can't use them. I
_thought_ that
Is there any nice plugin which I can run which will look at the
current project and tell me which plugins are out of date?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
yay! thx :-)
--jason
On Aug 14, 2008, at 10:57 PM, Eugene Kuleshov wrote:
Jason Dillon wrote:
Is there a decent size icon for Nexus somewhere... suitable for using
to setup a SSB via Fluidapp?
Jason, yo can try this one
http://www.nabble.com/file/p18984465/nx-big.png nx-big.png
Its been a while, but its finally out. Read about it more here:
http://groovy.codehaus.org/GMaven+-+1.0-rc-3+Release
Will probably take a few hours to sync to central. I'm pushing out
the new generated documentation now, which will take much longer I
suspect.
Cheers,
--jason
Findbugs plugin as
well as the SHITTY plugin and all is fine here.
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
Andres Almiray wrote:
Will give it a try with GB 0.7-SNAPSHOT and let you know. Like the
new
console upgrade :-)
Jason Dillon wrote:
I've just deployed a new set of snapshots
I've just deployed a new set of snapshots for GMaven 1.0-rc-3-
SNAPSHOT. This contains a bunch of stuff. See the road-map for more
details:
http://jira.codehaus.org/browse/MGROOVY?report=com.atlassian.jira.plugin.system.project:roadmap-panel
Anyways, just wanted folks to give this new
larger.
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Saturday, August 09, 2008 1:52 AM
To: Maven Developers List
Subject: Re: Decent size icon for Nexus?
You haven't played with Fluid yet?
http://fluidapp.com/
Its pimp, lets you make
Is there a decent size icon for Nexus somewhere... suitable for using
to setup a SSB via Fluidapp?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
, Jason Dillon [EMAIL PROTECTED] wrote:
Is there a decent size icon for Nexus somewhere... suitable for
using to setup a SSB via Fluidapp?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
+1
--jason
On Jul 18, 2008, at 8:58 AM, Oleg Gusakov wrote:
Hi,
16 issues fixed, no outstanding
Staging repo:
http://repository.sonatype.org:8081/nexus/content/repositories/staged-releases/maven-artifact/org/apache/maven/artifact/maven-artifact/3.0-alpha-1/
Staging site:
+1
--jason
On Jun 13, 2008, at 9:30 PM, John Casey wrote:
+1
-john
Jason van Zyl wrote:
Hi,
Oleg has been contributing patches to the artifact mechanism for
well over 6 months and has gone through some steps to look at graph-
based resolution, and subsequently moved on to the boolean
Just had a thought, would be nice if the pom exposed someway to define
aliases for a set of goals/phases.
This would allow project specific names to be used to invoke a set of
standard maven phases or a set of plugins.
Like I might want o have a release alias, which actually invokes:
Can I please get new snaps of the components/trunk and artifact/trunk
deployed please?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Are there any available tools (API level) to point at a maven
repository and navigate through it? (remote or local)? Perhaps to
scan for specific artifact types or something like that?
--jason
-
To unsubscribe, e-mail:
I've got a patch waiting which adds type information for collection
bits it uses... dunno where to post it.
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi, I've finally gotten around to integration maven-artifact w/
GShell... and I noticed that when resolving artifacts it tends to
prefer the repositories in dependency poms? Maybe its not a maven-
artifact thingy, but a maven-project thingy as I'm re-using the Maven
metadata source thingy.
Please :-) Sun is too bright, bring on the shade.
--jason
On May 21, 2008, at 10:07 PM, Jason van Zyl wrote:
I think if that many issues are resolved then release it. Can always
do another release.
On 20-May-08, at 11:39 AM, Daniel Kulp wrote:
A bunch of bugs have been fixed in the
Thanks, you should update its category so it shows up in the Maven
Technologies group list.
--jason
On May 21, 2008, at 10:09 PM, Brett Porter wrote:
MARTIFACT
On 22/05/2008, at 1:07 AM, Jason Dillon wrote:
I've got a patch waiting which adds type information for collection
bits
Um, why would you want to only support http?
--jason
On May 21, 2008, at 2:30 PM, Brett Porter wrote:
Hi Jason,
Is this related to your previous suggestion that we should only
support HTTP in Maven 2.1, or is there some other objective in mind?
Thanks,
Brett
2008/5/21 Jason van Zyl [EMAIL
Eh, seems like a simple fix as its only documentation.
I'd like to see 1.0 out, or perhaps a 1.0-rc-1 ASAP... regardless of
the documentation issues.
--jason
On May 16, 2008, at 4:36 PM, Jerome Lacoste wrote:
On Fri, May 16, 2008 at 10:27 AM, Arnaud HERITIER
[EMAIL PROTECTED] wrote:
Hi
Hi folks, can we change the maven-artifact 3.0 bits to _attach_
instead of _replace_ when retrotranslating? I'm consuming 3.0 for
GShell, which already requires Java 5, so the retrotranslation just
tacks on ~600k of stuff that I don't really need.
I'd like to just use the pure Java5
Did you commit this to svn, I don't see any changes...
--jason
On May 16, 2008, at 9:40 PM, Jason van Zyl wrote:
I've removed the retrotranslation from maven-artifact and deployed a
snapshot so give that a whirl.
On 16-May-08, at 4:44 AM, Jason Dillon wrote:
Hi folks, can we change
BTW, the new maven-artifact api kicks ass, so much easier to use
IMO... :-)
--jason
On May 16, 2008, at 9:40 PM, Jason van Zyl wrote:
I've removed the retrotranslation from maven-artifact and deployed a
snapshot so give that a whirl.
On 16-May-08, at 4:44 AM, Jason Dillon wrote:
Hi
Perhaps 2.1 needs to be changed to 2.2 and then 2.1 can be used for
what would be 2.0.10 + Java5
--jason
On May 4, 2008, at 6:32 PM, Marat Radchenko wrote:
+1 for 2.1, -1 for 2.0.10
On 5/4/08, nicolas de loof [EMAIL PROTECTED] wrote:
Hello,
As you can read at
know
Hervé
Le mercredi 23 avril 2008, Jason Dillon a écrit :
Anyone know what this warning means:
snip
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1-20080423.162027-1)
of type: maven-plugin; constructing POM artifact instead
+1
--jason
On Apr 25, 2008, at 5:10 AM, Raphaël Piéroni wrote:
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
Anyone know what this warning means:
snip
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1-20080423.162027-1)
of type: maven-plugin; constructing POM artifact instead. ?
/snip
Not specific to the ianal plugin, but gmaven
+1
--jason
On Apr 19, 2008, at 1:39 AM, Raphaël Piéroni wrote:
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
+1
---jason
On Apr 11, 2008, at 5:22 AM, Raphaël Piéroni wrote:
Hi,
We solved 20 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
+1
--jason
On Apr 7, 2008, at 11:42 PM, Brian E. Fox wrote:
Time to vote on the final Maven 2.0.9 Release. We went through 8
Release
Candidates and fixed all know regressions from 2.0.8 to 2.0.9 during
that time. Note that there were no source changes between RC8 and this
final build.
Are you using beta-6 w/o any problems? I can't get it to generate
proper links at all :-(
--jason
On Apr 3, 2008, at 3:26 AM, Brian E. Fox wrote:
I think it's safer to leave it at beta-6. Most people aren't
expressing any issues and if anyone has trouble, they can manually
lock to
Anyone know how to do this?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hiya, I'm having some problem getting my archetype module installed
into my local repository (haven't tried a remote deploy yet) with
a .jar extention. It always puts the archive into the repo with
a .maven-archetype ext, which causes problems when trying to actually
use the archetype:
Hiya, how can we get the default behavior of plugins which use
velocity to be less verbose?
I see muck like this which I'd rather not:
snip
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property:
:-(
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
, at 12:19 AM, Jason Dillon wrote:
Is the new maven-artifact ready for prime-time? Any idea when it
might get released?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
Is the new maven-artifact ready for prime-time? Any idea when it
might get released?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
--jason
On Mar 17, 2008, at 10:18 PM, Daniel Kulp wrote:
Several projects are sucessfully using remote-resources so it's time
pull
it out of beta and do the 1.0 release. :-)
This version provides three new improvements from 1.0-beta-2:
** Improvement
* [MRRESOURCES-22] - Provide
Does this bundle have the same bits as the legal-bundle from genesis
does?
--jason
On Mar 17, 2008, at 10:05 PM, Daniel Kulp wrote:
To comply with the latest requirements discussed on legal-discuss, we
need a new version of the apache-jar-resource-bundle.
The only change is really the
+1
--jason
On Mar 17, 2008, at 10:12 PM, Daniel Kulp wrote:
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
Is there an RSS feed somewhere to track changes to the central
repository?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thx :-)
--jason
On Mar 14, 2008, at 2:52 PM, Dan Tran wrote:
I use this feed
http://www.mvnrepository.com/feeds/rss2.0.xml
On Fri, Mar 14, 2008 at 12:34 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
Is there an RSS feed somewhere to track changes to the central
repository?
--jason
Any reason why after running shade that the project.basedir becomes
project.build.directory ?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
--jason
On Mar 2, 2008, at 10:20 AM, Brett Porter wrote:
Hi,
The Shade plugin is ready to be released. This is needed for the
2.0.9 release as well.
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540styleName=Htmlversion=13994
The remaining issues
to dealing with more
verbosity, you should interview at Atlassian? :)
On 12/02/2008, at 4:47 PM, Don Brown wrote:
Atlassian is hiring ... :)
On 2/12/08, Jason Dillon [EMAIL PROTECTED] wrote:
IMO we should strive to make the pom even more verbose... So all us
maven folk can keep our jobbies
Developers List dev@maven.apache.org
Subject: Re: An Attribute Based POM
Are you saying that if you are looking forward to dealing with more
verbosity, you should interview at Atlassian? :)
On 12/02/2008, at 4:47 PM, Don Brown wrote:
Atlassian is hiring ... :)
On 2/12/08, Jason Dillon [EMAIL
IMO we should strive to make the pom even more verbose... So all us maven folk
can keep our jobbies :-P
--jason
-Original Message-
From: Brett Porter [EMAIL PROTECTED]
Date: Tue, 12 Feb 2008 16:35:35
To:Maven Developers List dev@maven.apache.org
Subject: Re: An Attribute Based POM
As mentioned before I'm not a big fan of merging these plugins. IMO,
SHITTY provides a lot of additional functionality on top of what the
maven-invoker-plugin provides, like:
* Groovy integration
* More flexible configuration
* Clean and install support integrated (for less pom.xml
+1
--jason
On Jan 17, 2008, at 3:22 PM, Daniel Kulp wrote:
Well, I'd prefer to not get into version number arguments as it
really
just doesn't matter.Hell, we have plugins (like the release
plugin,
dependency plugin, etc..) that EVERYONE uses that haven't had a real
release and
I'm personally not very interested in merging the plugins. I can
explain more when I'm back from Thailand :-)
--jason
On Dec 18, 2007, at 3:13 PM, Jason van Zyl wrote:
On 17 Dec 07, at 12:17 AM 17 Dec 07, olivier lamy wrote:
Hi,
Agree on merge but in a new plugin or merging in
+1
--jason
-Original Message-
From: Daniel Kulp [EMAIL PROTECTED]
Date: Wed, 12 Dec 2007 12:00:48
To:dev@maven.apache.org
Subject: Re: [Vote][take 2] maven-shade-plugin release 1.0-alpha-15 and move
out of sandbox
+1 to both the release and moving out of sandbox.
Looking forward
+1
--jason
-Original Message-
From: Daniel Kulp [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 10:55:14
To:Maven Developers List dev@maven.apache.org
Subject: [VOTE] maven-remote-resources-plugin 1.0-beta-2
I'd like to release version 1.0-beta-2 of the
maven-remote-resources-plugin. The
1 - 100 of 392 matches
Mail list logo