[
https://issues.apache.org/jira/browse/EMAIL-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472559
]
Bindul Bhowmik commented on EMAIL-63:
-
Here is my understanding and resolution of the problem:
One of the
[
https://issues.apache.org/jira/browse/SCXML-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472560
]
Wolfgang Frech commented on SCXML-38:
-
ad b) non-unique state ids
My test cases use the same ID intentionally.
I
[
https://issues.apache.org/jira/browse/EMAIL-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472562
]
Ben Speakmon commented on EMAIL-63:
---
Ohhh, I get it. You're right. By all means, put it in there.
Maven 2 pom.xml
Luc Maisonobe wrote on Monday, February 12, 2007 11:01 PM:
Rahul Akolkar wrote :
On 2/12/07, Luc Maisonobe [EMAIL PROTECTED] wrote:
Yes, it seems many files have strange settings. I use a Linux box
and on a fresh checkout, I get some files with DOS-like line
endings. If I set them to a
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Jakarta-commons Wiki
for change notification.
The following page has been changed by WolfgangFrech:
http://wiki.apache.org/jakarta-commons/SCXML/Tutorials/Templating
Hi Hen,
Henri Yandell wrote on Tuesday, February 13, 2007 7:00 AM:
Second try - having had it explained to me on #maven why relocating is
important [so commons-lang:commons-lang 2.1 and
org.apache.commons:commons-lang 3.0 are considered the same and a
transitive clash can be recognized].
[
https://issues.apache.org/jira/browse/EMAIL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472592
]
Piero Ottuzzi commented on EMAIL-62:
Hi Dion, all,
commons-email 1.0 is quite broken and I think we need to move
Changes against VFS-1_0-RC8-SNAPSHOT to use LocalFiles and Webdav files
---
Key: VFS-110
URL: https://issues.apache.org/jira/browse/VFS-110
Project: Commons VFS
Issue Type:
[
https://issues.apache.org/jira/browse/VFS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles Gaillard updated VFS-110:
Attachment: common-vfs-cvs-13_02_2007.zip
commons-vfs-svn-VFS-1_0-RC8-SNAPSHOT.zip
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-soap has an issue affecting its community
integration.
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-jelly-tags-soap has an issue affecting its community
integration.
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-jelly-tags-jaxme has an issue affecting its community
integration.
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-jelly-tags-jaxme has an issue affecting its community
integration.
This
On 2/13/07, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi Hen,
Henri Yandell wrote on Tuesday, February 13, 2007 7:00 AM:
Second try - having had it explained to me on #maven why relocating is
important [so commons-lang:commons-lang 2.1 and
org.apache.commons:commons-lang 3.0 are considered the
You need to create a relocation POM for the release that does relocation to
avoid hundred users to ask for upload on ibilio.
The relocation POM will produce a warning on console for maven users. You
can expect users to consider warnings and update groupId.
The relocation POM will not be required
[
https://issues.apache.org/jira/browse/NET-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Aggarwal updated NET-151:
--
Attachment: FTPClientOverrideHost.patch.txt
Steffen Heil [EMAIL PROTECTED] suggested to use a method with
Vote passed with +1s from:
(PMC)
Niall Pemberton
Gary Gregory
Stephen Colebourne
Rahul Akolkar
Simon Kitching (voted on RC1)
(non-PMC)
Jörg Schaible
Release will go out today.
Hen
On 2/9/07, Henri Yandell [EMAIL PROTECTED] wrote:
Going with RC3:
[Apologies for spam...]
Jörg Schaible is on the PMC too. I missed his name in the list when scanning.
Hen
On 2/13/07, Henri Yandell [EMAIL PROTECTED] wrote:
Vote passed with +1s from:
(PMC)
Niall Pemberton
Gary Gregory
Stephen Colebourne
Rahul Akolkar
Simon Kitching (voted on RC1)
Vote passed for Lang 2.3.
+1s from:
(PMC)
Jörg Schaible
Niall Pemberton
Oliver Heger
Gary Gregory
Rahul Akolkar
Stephen Colebourne (voted on RC1)
The release will go out today.
Hen
On 2/9/07, Henri Yandell [EMAIL PROTECTED] wrote:
Here's the 3rd release candidate for Lang 2.3:
Author: bayard
Date: Tue Feb 13 08:30:47 2007
New Revision: 507079
URL: http://svn.apache.org/viewvc?view=revrev=507079
Log:
Moving to 1.4-SNAPSHOT
Modified:
jakarta/commons/proper/io/trunk/build.xml
jakarta/commons/proper/io/trunk/pom.xml
jakarta/commons/proper/io/trunk/project.xml
Author: bayard
Date: Tue Feb 13 08:31:25 2007
New Revision: 507081
URL: http://svn.apache.org/viewvc?view=revrev=507081
Log:
Moving to the next version - which I'm claiming will be 3.0
Modified:
jakarta/commons/proper/lang/trunk/default.properties
Author: bayard
Date: Tue Feb 13 08:53:07 2007
New Revision: 507089
URL: http://svn.apache.org/viewvc?view=revrev=507089
Log:
Releasing Lang 2.3 from the rc3
Added:
jakarta/commons/proper/lang/tags/LANG_2_3/
- copied from r507088, jakarta/commons/proper/lang/tags/LANG_2_3_RC3/
Author: bayard
Date: Tue Feb 13 08:53:32 2007
New Revision: 507090
URL: http://svn.apache.org/viewvc?view=revrev=507090
Log:
Releasing IO 1.3.1 from the rc3
Added:
jakarta/commons/proper/io/tags/IO_1_3_1/
- copied from r507089, jakarta/commons/proper/io/tags/IO_1_3_1_RC3/
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.
* keys good, md5s good.
* source compiles happily with maven1 and has the same number of files
in as the published jar.
* site looks good.
+1
Remember to deploy the jar and pom to the m1 repository when releasing
(as they're not in the rc).
Hen
On 2/11/07, Phil Steitz [EMAIL PROTECTED] wrote:
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.
Author: olegk
Date: Tue Feb 13 10:01:48 2007
New Revision: 507122
URL: http://svn.apache.org/viewvc?view=revrev=507122
Log:
HTTPCLIENT-630: Made readObject/writeObject methods private
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/URI.java
Thanks for bringing this up Henri.
Here's my view on this:
1. Maven 1 builds stay as commons-foo (like you said)
2. Maven 2 builds change to org.apache.commons once the component moves
to using M2 to build the component *and* putting the artifacts into the
M2 repo. This should be done one
Author: olegk
Date: Tue Feb 13 10:18:05 2007
New Revision: 507134
URL: http://svn.apache.org/viewvc?view=revrev=507134
Log:
HTTPCLIENT-631: RFC2109Spec#SET_COOKIE_KEY, RFC2965Spec#SET_COOKIE2_KEY static
variables made final
Modified:
you can change the old poms to relocate to a new location as long as
the new location has the same old jars and poms (just groupId change).
IIRC your case was different.
So, I' see two options for relocation:
1) when new version is out with new groupId add relocation pom in old
location just
Author: olegk
Date: Tue Feb 13 10:34:15 2007
New Revision: 507149
URL: http://svn.apache.org/viewvc?view=revrev=507149
Log:
HTTPCLIENT-632: Removed superfluous null check
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HttpHost.java
Modified:
oh there's a 3rd option that I even like more
3) make new releases in new groupid, no relocations at all
+ easiest ;)
+ users trying to upgrade will need to know that the groupId has
changed and act by themselves, so they will be involved, and in case
of classpath problems they will know what
[
https://issues.apache.org/jira/browse/EMAIL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472839
]
Ben Speakmon commented on EMAIL-62:
---
I'm with Dion 100% on meeting the needs of users, but as I said on the list, I
Author: dennisl
Date: Tue Feb 13 11:24:09 2007
New Revision: 507169
URL: http://svn.apache.org/viewvc?view=revrev=507169
Log:
Add maven-gpg-plugin to the release and rc profiles.
Modified:
jakarta/commons/proper/commons-parent/trunk/pom.xml
Modified:
I don't understand the distinction you make between scenario 1 and 3 :
if new release use a relocation pom under commons-xxx and DOESN'T deploy a
jar under this group
- maven2 users will get relocated artifact + a warning to update
dependencies
- maven1 users will not get the new version, may
scenario 3 is with no relocation pom at all, so users get involved by
having to explicitly change the groupId
On 2/13/07, nicolas de loof [EMAIL PROTECTED] wrote:
I don't understand the distinction you make between scenario 1 and 3 :
if new release use a relocation pom under commons-xxx and
Author: dennisl
Date: Tue Feb 13 12:38:19 2007
New Revision: 507204
URL: http://svn.apache.org/viewvc?view=revrev=507204
Log:
Add javadoc, jxr, surefire and jdepend reports.
Modified:
jakarta/commons/proper/commons-parent/trunk/pom.xml
Modified:
Author: oheger
Date: Tue Feb 13 12:54:15 2007
New Revision: 507212
URL: http://svn.apache.org/viewvc?view=revrev=507212
Log:
CONFIGURATION-237: Added ManagedReloadingStrategy. Thanks to Nicolas de Loof
Added:
[
https://issues.apache.org/jira/browse/CONFIGURATION-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-237.
Resolution: Fixed
Fix Version/s: (was: 1.5)
[
https://issues.apache.org/jira/browse/CONFIGURATION-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger updated CONFIGURATION-249:
---
Fix Version/s: (was: 1.4)
1.5
save to URLs with a
Author: oheger
Date: Tue Feb 13 13:02:09 2007
New Revision: 507219
URL: http://svn.apache.org/viewvc?view=revrev=507219
Log:
Fixed a checkstyle warning
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/DefaultConfigurationBuilder.java
Modified:
...for making it into Java Developers Journal's
The Top 150 i-Technology Heroes of Today and Yesteryear
Read all about it here:
http://java.sys-con.com/read/33.htm
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL
Author: jochen
Date: Tue Feb 13 13:15:09 2007
New Revision: 507231
URL: http://svn.apache.org/viewvc?view=revrev=507231
Log:
Added the rat-maven-plugin.
Modified:
jakarta/commons/proper/fileupload/branches/b1_2/pom.xml
Modified: jakarta/commons/proper/fileupload/branches/b1_2/pom.xml
URL:
Author: oheger
Date: Tue Feb 13 13:20:43 2007
New Revision: 507232
URL: http://svn.apache.org/viewvc?view=revrev=507232
Log:
Updated release notes
Modified:
jakarta/commons/proper/configuration/trunk/RELEASE-NOTES.txt
Modified: jakarta/commons/proper/configuration/trunk/RELEASE-NOTES.txt
Author: oheger
Date: Tue Feb 13 13:23:56 2007
New Revision: 507233
URL: http://svn.apache.org/viewvc?view=revrev=507233
Log:
Added Nicolas De Loof to the list of contributors
Modified:
jakarta/commons/proper/configuration/trunk/pom.xml
Raymond, Brian wrote:
I have been banging my head against the wall for hours trying to write a
data/ element back into an OSX XML plist file. I use the following to
successfully read the element:
byte[] tmpByte = (byte[])settings.getProperty(node.name)
I then modify it but I cannot for the
Author: jochen
Date: Tue Feb 13 13:33:38 2007
New Revision: 507236
URL: http://svn.apache.org/viewvc?view=revrev=507236
Log:
Creating 1.2rc4.
Modified:
jakarta/commons/proper/fileupload/branches/b1_2/pom.xml
jakarta/commons/proper/fileupload/branches/b1_2/src/changes/changes.xml
Author: luc
Date: Tue Feb 13 14:06:30 2007
New Revision: 507253
URL: http://svn.apache.org/viewvc?view=revrev=507253
Log:
allow using locales with different variants
Modified:
jakarta/commons/proper/math/trunk/src/java/org/apache/commons/math/MathException.java
Modified:
[
https://issues.apache.org/jira/browse/EMAIL-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472922
]
Ben Speakmon commented on EMAIL-6:
--
My current thinking on this:
I'm not convinced that it's useful to support
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Jakarta-commons Wiki
for change notification.
The following page has been changed by BenSpeakmon:
http://wiki.apache.org/jakarta-commons/Email
The comment on the change is:
Added list of current open issues with status and
[
https://issues.apache.org/jira/browse/EMAIL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472933
]
Bindul Bhowmik commented on EMAIL-64:
-
I have started to move the test cases over to using Wiser. However, I found
Author: jochen
Date: Tue Feb 13 18:35:56 2007
New Revision: 507361
URL: http://svn.apache.org/viewvc?view=revrev=507361
Log:
Added the rat-maven-plugins report.
Modified:
jakarta/commons/proper/commons-parent/trunk/pom.xml
Modified: jakarta/commons/proper/commons-parent/trunk/pom.xml
URL:
Author: jochen
Date: Tue Feb 13 19:24:25 2007
New Revision: 507375
URL: http://svn.apache.org/viewvc?view=revrev=507375
Log:
Got it finally working to add LICENSE and NOTICE to -sources.jar
and -javadoc.jar, while at the same time building the assemblies.
Modified:
Author: jochen
Date: Tue Feb 13 19:29:22 2007
New Revision: 507376
URL: http://svn.apache.org/viewvc?view=revrev=507376
Log:
Fixed the wrong version number.
Modified:
jakarta/commons/proper/fileupload/branches/b1_2/xdocs/index.xml
Modified:
Perhaps this should have an @since tag added, as it's a new method?
[EMAIL PROTECTED] wrote:
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/AutoCloseInputStream.java
URL:
Author: jochen
Date: Tue Feb 13 20:16:50 2007
New Revision: 507379
URL: http://svn.apache.org/viewvc?view=revrev=507379
Log:
Adding the commons-fileupload logo.
Modified:
jakarta/commons/proper/fileupload/branches/b1_2/src/site/site.xml
Modified:
[
https://issues.apache.org/jira/browse/EMAIL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472974
]
Ben Speakmon commented on EMAIL-64:
---
I wouldn't be happy with requiring JDK 1.5 to build, especially since no code
Author: jochen
Date: Tue Feb 13 20:17:19 2007
New Revision: 507380
URL: http://svn.apache.org/viewvc?view=revrev=507380
Log:
The maven-site-plugin doesn't add static resources. :-(
Modified:
jakarta/commons/proper/fileupload/branches/b1_2/pom.xml
Modified:
[
https://issues.apache.org/jira/browse/EMAIL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472978
]
dion gillard commented on EMAIL-64:
---
I'm with Ben.
Use wiser instead of dumbster for test cases
Author: jochen
Date: Tue Feb 13 20:48:41 2007
New Revision: 507386
URL: http://svn.apache.org/viewvc?view=revrev=507386
Log: (empty)
Added:
jakarta/commons/proper/fileupload/tags/commons-fileupload-1.2rc4/
- copied from r507385, jakarta/commons/proper/fileupload/branches/b1_2/
[
https://issues.apache.org/jira/browse/EMAIL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472982
]
Bindul Bhowmik commented on EMAIL-64:
-
I agree too, needed to confirm it with others though.
I will attach a
Hi,
this is going to kill me, but I'd like to call for a release of
commons-fileupload 1.2 once more. Commons-fileupload-1.2rc4 is
available from
http://people.apache.org/~jochen/commons-fileupload/dist
The generated site is at
http://people.apache.org/~jochen/commons-fileupload/dist
[
https://issues.apache.org/jira/browse/EMAIL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472986
]
dion gillard commented on EMAIL-62:
---
Does anyone know why we're patching a Maven-generated build.xml file instead of
[
https://issues.apache.org/jira/browse/EMAIL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472996
]
Ben Speakmon commented on EMAIL-62:
---
I didn't know how to generate a build.xml from maven at the time. I have no
What in such a scenario :
My project depends commons-xxx-1.2, relocated at org.apache.commons.xxx-1.2
My pom get transitive commons-xxx-1.1
If I DON't update my POM maven2 will find the relocated artifact and exclude
1.1 - that's fine
If 1.1 has no relocated POM, and if I update my POM, maven2
right a relocate pom for ALL versions is required to avoid duplication
on classpath
BUT as I said almost everybody will have cached previous versions of
commons so they won't see the relocation until they delete local repo
and the poms with relocation info get downloaded.
On 2/13/07, nicolas de
Hi Carlos,
Carlos Sanchez wrote on Tuesday, February 13, 2007 7:29 PM:
you can change the old poms to relocate to a new location as long as
the new location has the same old jars and poms (just groupId
change). IIRC your case was different.
So, I' see two options for relocation:
1)
According to this, when relocation projectX for new release N+1
option 1 : making dependency to oldGroupId:N+1 will work, but making
dependency to newGroupId:N+1 will introduce duplicate jars issues if other
dependencies introduce transitive-dependency to oldGroupId:N
option 2 : relocating all
iirc you have very different jars in the two groupids, that's not
relocation, that would actually change the binaries for users
On 2/13/07, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi Carlos,
Carlos Sanchez wrote on Tuesday, February 13, 2007 7:29 PM:
you can change the old poms to relocate to
On 2/13/07, nicolas de loof [EMAIL PROTECTED] wrote:
According to this, when relocation projectX for new release N+1
option 1 : making dependency to oldGroupId:N+1 will work, but making
dependency to newGroupId:N+1 will introduce duplicate jars issues if other
dependencies introduce
Author: jochen
Date: Tue Feb 13 23:55:39 2007
New Revision: 507429
URL: http://svn.apache.org/viewvc?view=revrev=507429
Log:
Changing groupId to org.apache.commons.fileupload for 1.3.
Modified:
jakarta/commons/proper/fileupload/trunk/build.xml
73 matches
Mail list logo
