You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Dennis Lundberg (JIRA)" <ji...@apache.org> on 2006/05/22 19:49:32 UTC
[jira] Commented: (MODELER-3) [modeler] maven build fails on os x
with test failure.
[ http://issues.apache.org/jira/browse/MODELER-3?page=comments#action_12412810 ]
Dennis Lundberg commented on MODELER-3:
---------------------------------------
This can be resolved by upgrading mx4j from 1.1 to 2.1.1 in project.xml. Note that the new version of mx4j requires Java 1.3, but if you are on OS X that's not a problem.
> [modeler] maven build fails on os x with test failure.
> ------------------------------------------------------
>
> Key: MODELER-3
> URL: http://issues.apache.org/jira/browse/MODELER-3
> Project: Commons Modeler
> Type: Bug
> Environment: Operating System: other
> Platform: Other
> Reporter: David Jencks
>
> maven build fails on os x with test failure. The failure occurs on the first
> test run, following tests pass. Stack trace:
> Testcase:
> testModelMBeanAttributeInfo(org.apache.commons.modeler.RegistryTestCase): Caused
> an ERROR
> nested exception is java.lang.IllegalArgumentException: Invalid descriptor
> javax.management.RuntimeOperationsException: nested exception is
> java.lang.IllegalArgumentException: Invalid descriptor
> java.lang.IllegalArgumentException: Invalid descriptor
> at
> javax.management.modelmbean.ModelMBeanNotificationInfo.setDescriptor(ModelMBeanNotificationInfo.java:67)
> at
> org.apache.commons.modeler.NotificationInfo.createNotificationInfo(NotificationInfo.java:117)
> at org.apache.commons.modeler.ManagedBean.createMBeanInfo(ManagedBean.java:429)
> at
> org.apache.commons.modeler.RegistryTestCase.testModelMBeanAttributeInfo(RegistryTestCase.java:124)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site]Sites for snapshots published
Posted by Phil Steitz <ph...@gmail.com>.
On 5/22/06, robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> On Mon, 2006-05-22 at 20:45 +0200, Oliver Heger wrote:
> > Hi,
> >
> > I just noticed that recently the sites of some components have been
> > deployed directly from their svn trunk. So the sites refer to snapshot
> > versions (e.g. BeanUtils, Configuration, Math, ...). Was this done by
> > intension?
>
> yep - i did it. i went through and changed siteAddress then redeployed
> each site.
>
> please feel free to jump in and redeploy anything that isn't right.
>
> > It might be confusing for users if the sites describe features that are
> > not contained in the latest releases.
>
> IMHO it's a trade off. users get to see all the features that are
> available but have to actively search for documentation related to the
> version they have downloaded.
>
> many components provide link to the released documentation (for example
> http://jakarta.apache.org/commons/logging/) though it would probably be
> a good idea to add an indication on the navigation bar that these
> documents apply to the latest code...
That is a best practice that at least [collections], [math] and [lang]
at least all use. The important thing is to have the javadoc links
correctly labelled in the nav, so users can find "svn latest" or
"x.y-SNAPSHOT" and clearly distinguish this from the latest (and maybe
some previous) release(s).
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site]Sites for snapshots published
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Mon, 2006-05-22 at 20:45 +0200, Oliver Heger wrote:
> Hi,
>
> I just noticed that recently the sites of some components have been
> deployed directly from their svn trunk. So the sites refer to snapshot
> versions (e.g. BeanUtils, Configuration, Math, ...). Was this done by
> intension?
yep - i did it. i went through and changed siteAddress then redeployed
each site.
please feel free to jump in and redeploy anything that isn't right.
> It might be confusing for users if the sites describe features that are
> not contained in the latest releases.
IMHO it's a trade off. users get to see all the features that are
available but have to actively search for documentation related to the
version they have downloaded.
many components provide link to the released documentation (for example
http://jakarta.apache.org/commons/logging/) though it would probably be
a good idea to add an indication on the navigation bar that these
documents apply to the latest code...
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[site]Sites for snapshots published
Posted by Oliver Heger <ol...@oliver-heger.de>.
Hi,
I just noticed that recently the sites of some components have been
deployed directly from their svn trunk. So the sites refer to snapshot
versions (e.g. BeanUtils, Configuration, Math, ...). Was this done by
intension?
It might be confusing for users if the sites describe features that are
not contained in the latest releases.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org