You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Scott Deboy <sd...@comotivsystems.com> on 2007/11/15 21:02:01 UTC
log4j breaking maven builds
Can we get the maven dependencies corrected so we don't break maven and
others?
See
http://www.1060.org/blogxter/entry?publicid=9FDCA6751DE11295AD0049F5DB17
F461&token=
Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Office: 503.224.7496
Direct Line: 503.821.6482
Cell: 503.997.1367
Fax: 503.222.0185
sdeboy@comotivsystems.com
www.comotivsystems.com
-----Original Message-----
From: Curt Arnold [mailto:carnold@apache.org]
Sent: Thursday, November 15, 2007 11:19 AM
To: Log4J Developers List
Subject: Re: [PROPOSAL] SocketHubAppender change - allow auto port
choice
I've logged a bug report (43874) for the SocketHubAppender
enhancement and committed the createServerSocket() patch and updated
the changes.xml for 1.2.16. I'm not saying that has to be the final
approach, but I think there is general agreement that we can do
something minimal and safe in 1.2.16 that would allow zeroconf to
work in this case and so moving the discussion to a bug report and
using the SVN to iterate is probably a better process.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: log4j breaking maven builds
Posted by Curt Arnold <ca...@apache.org>.
On Nov 15, 2007, at 2:02 PM, Scott Deboy wrote:
> Can we get the maven dependencies corrected so we don't break maven
> and
> others?
>
> See
> http://www.1060.org/blogxter/entry?
> publicid=9FDCA6751DE11295AD0049F5DB17
> F461&token=
>
Its fixed in the subversion repo. All that would be necessary is to
do a 1.2.16 release. There isn't a good mechanism for changing the
metadata after a release.
There was a suggestion to set the scope to "provided", but from my
reading that isn't appropriate since if you are running or building
JMX or JMS on a J2SE environment those aren't provided by the JRE,
though they would be if you were running on a J2EE. Guess we could
ask on the maven-user list for a definitive suggestion, but I think
optional is appropriate and provided is wrong.
We aren't breaking the building of Maven or Ivy itself as far as I
know. Only that projects built with Maven or Ivy that upgrade to
1.2.15, it should be fixed, but it should not break anyone without a
first action on their part.
So I guess the right action is to proceed with a 1.2.16 release. If
you have any issues that you think must be in 1.2.16, add them as
blockers to bug 43313.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org