On 4/1/07, Torsten Curdt [EMAIL PROTECTED] wrote:
I've noticed that the plugin versions are not specified in the
commons parent pom. From my experience this is a *really* bad idea as
maven then picks the most recent from local repository. Which again
can easily lead to inconsistent site builds
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability. Otherwise we just deal
with whatever pain Maven is throwing everyone's way and yell at them
to fix.
Er why? It is not our job to be gump and test commons builds
[
https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485958
]
Harald Brabenetz commented on VFS-120:
--
I found a Workaround:
I don't use the VFS.getManager(). Instead i create
On 02.04.2007, at 09:49, Stephen Colebourne wrote:
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability.
...and then have the project define the reports they want?
Otherwise we just deal
with whatever pain Maven
[
https://issues.apache.org/jira/browse/FILEUPLOAD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485970
]
Oleg Kalnichevski commented on FILEUPLOAD-131:
--
Folks,
I doubt HttpCore would be of any use here,
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
On 02.04.2007, at 09:49, Stephen Colebourne wrote:
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability.
...and then have the project define the reports they
Torsten Curdt wrote on Sunday, April 01, 2007 2:17 PM:
I've noticed that the plugin versions are not specified in the
commons parent pom. From my experience this is a *really* bad
idea as
maven then picks the most recent from local repository. Which again
can easily lead to inconsistent site
[
https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485984
]
Mario Ivankovits commented on VFS-120:
--
As a workaround you can do it that way, as long as you do not use this
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-id has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-id has an issue affecting its community integration.
This issue affects
[
https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485992
]
Harald Brabenetz commented on VFS-120:
--
I'm happy about the Workaround. It makes also a clean connection.open()
[
https://issues.apache.org/jira/browse/VFS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harald Brabenetz updated VFS-120:
-
Attachment: SftpFileSystem-patch.txt
see last comment
SFTP-Exception:
Torsten Curdt tcurdt at apache.org writes:
As already announced I would like to move
http://jakarta.apache.org/commons/sandbox/jci/
out of the sandbox so I can then prepare a first RC. Please cast your
votes for the graduation!
Despite the result already posted:
+1
Joerg
BeanUtils cannot set property of type Long with value of Double
---
Key: BEANUTILS-274
URL: https://issues.apache.org/jira/browse/BEANUTILS-274
Project: Commons BeanUtils
Issue
[
https://issues.apache.org/jira/browse/BEANUTILS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Liberato updated BEANUTILS-273:
---
Fix Version/s: (was: 1.8.0)
Affects Version/s: 1.7.0
updating
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-fmt-test has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-fmt-test has an issue affecting its community
integration.
Support of HTTP headers
---
Key: VFS-121
URL: https://issues.apache.org/jira/browse/VFS-121
Project: Commons VFS
Issue Type: Improvement
Affects Versions: Nightly Builds
Reporter: Philippe Poulard
Author: psteitz
Date: Mon Apr 2 13:39:33 2007
New Revision: 524915
URL: http://svn.apache.org/viewvc?view=revrev=524915
Log:
tagging release (copied from RC3 tag).
Added:
jakarta/commons/proper/dbcp/tags/DBCP_1_2_2/
- copied from r522358,
Henri Yandell wrote:
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
On 02.04.2007, at 09:49, Stephen Colebourne wrote:
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability.
...and then have the project define
Torsten Curdt wrote:
I've noticed that the plugin versions are not specified in the commons
parent pom. From my experience this is a *really* bad idea as maven then
picks the most recent from local repository. Which again can easily lead
to inconsistent site builds across the team. So if no
Author: tcurdt
Date: Mon Apr 2 15:27:41 2007
New Revision: 524951
URL: http://svn.apache.org/viewvc?view=revrev=524951
Log:
enable the gpg plugin
Modified:
jakarta/commons/proper/jci/trunk/pom.xml
Modified: jakarta/commons/proper/jci/trunk/pom.xml
URL:
Author: tcurdt
Date: Mon Apr 2 15:31:22 2007
New Revision: 524954
URL: http://svn.apache.org/viewvc?view=revrev=524954
Log:
ignore cobertura files
Modified:
jakarta/commons/proper/jci/trunk/ (props changed)
jakarta/commons/proper/jci/trunk/compilers/eclipse/ (props changed)
Guys,
Do we already have docs on how to do commmons releases with maven2
somewhere?
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Author: tcurdt
Date: Mon Apr 2 16:00:30 2007
New Revision: 524960
URL: http://svn.apache.org/viewvc?view=revrev=524960
Log:
use gpg plugin from parent,
define some properties for the parent pom
Modified:
jakarta/commons/proper/jci/trunk/pom.xml
Modified:
Author: tcurdt
Date: Mon Apr 2 16:10:58 2007
New Revision: 524961
URL: http://svn.apache.org/viewvc?view=revrev=524961
Log:
[maven-release-plugin] prepare release 1.0-RC1
Modified:
jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml
Author: tcurdt
Date: Mon Apr 2 16:11:16 2007
New Revision: 524962
URL: http://svn.apache.org/viewvc?view=revrev=524962
Log:
[maven-scm] copy for tag 1.0-RC1
Added:
jakarta/commons/proper/jci/tags/1.0-RC1/
- copied from r524960, jakarta/commons/proper/jci/trunk/
Author: tcurdt
Date: Mon Apr 2 16:11:29 2007
New Revision: 524963
URL: http://svn.apache.org/viewvc?view=revrev=524963
Log:
[maven-release-plugin] prepare for next development iteration
Modified:
jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
Guys,
Do we already have docs on how to do commmons releases with maven2
somewhere?
No. Once [dbcp] is out (pushing it out as we speak), do we expect any
more 1.x releases? If not, we should just update the releasing docs
to m2.
Phil
On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
Guys,
Do we already have docs on how to do commmons releases with maven2
somewhere?
No. Once [dbcp] is out (pushing it out as we speak), do we expect any
more 1.x releases? If not, we should
On 03.04.2007, at 01:34, Phil Steitz wrote:
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
Guys,
Do we already have docs on how to do commmons releases with maven2
somewhere?
No. Once [dbcp] is out (pushing it out as we speak), do we expect any
more 1.x releases? If not, we should
On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote:
On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
Guys,
Do we already have docs on how to do commmons releases with maven2
somewhere?
No. Once [dbcp] is out (pushing it out as we
I think the end should be nigh for Jakarta (those on private@ will
have seen a thread in which I side-topic'd with the feeling that the
end should be nigh for Jakarta). Previously I've suggested that
Commons should flatten into Jakarta and that Jakarta should become a
general 'Java components'
On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote:
I think the end should be nigh for Jakarta (those on private@ will
have seen a thread in which I side-topic'd with the feeling that the
end should be nigh for Jakarta). Previously I've suggested that
Commons should flatten into Jakarta and that
On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote:
So with that said - I'd like to propose that we move to commons.apache.org.
+1
We have talked about this lots of times before and some discussions
have had us breaking commons itself apart
How do we retrieve the HTTP Headers in the request?
---
Key: FILEUPLOAD-132
URL: https://issues.apache.org/jira/browse/FILEUPLOAD-132
Project: Commons FileUpload
Issue Type: Wish
Affects
38 matches
Mail list logo
