[JBoss JIRA] Created: (JBAS-9435) Compile JBoss 6.1 with JDK 6
by Frank Langelage (JIRA)
Compile JBoss 6.1 with JDK 6
----------------------------
Key: JBAS-9435
URL: https://issues.jboss.org/browse/JBAS-9435
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: 6.0.0.Final
Reporter: Frank Langelage
Assignee: Paul Gier
JBoss AS 6.x requires JDK 6 AFAIK. But the source is compiled with source / target 1.5.
To change this I changed pom.xml like this:
Index: jboss-head/pom.xml
===================================================================
--- jboss-head/pom.xml (revision 111957)
+++ jboss-head/pom.xml (working copy)
@@ -51,8 +51,8 @@
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
- <source>1.5</source>
- <target>1.5</target>
+ <source>1.6</source>
+ <target>1.6</target>
<showDeprecation>false</showDeprecation>
<showWarnings>false</showWarnings>
</configuration>
To compile successfully I had to change one file:
Index: jboss-head/varia/src/main/java/org/jboss/jdbc/HypersonicDatabase.java
===================================================================
--- jboss-head/varia/src/main/java/org/jboss/jdbc/HypersonicDatabase.java (revision 111957)
+++ jboss-head/varia/src/main/java/org/jboss/jdbc/HypersonicDatabase.java (working copy)
@@ -36,7 +36,7 @@
/**
* Integration with <a href="http://sourceforge.net/projects/hsqldb">HSQLDB</a>
*
- * @author <a href="mailto:rickard.oberg@telkel.com">Rickard �berg</a>
+ * @author <a href="mailto:rickard.oberg@telkel.com">Rickard Öberg</a>
* @author <a href="mailto:Scott_Stark@displayscape.com">Scott Stark</a>.
* @author <a href="mailto:pf@iprobot.com">Peter Fagerlund</a>
* @author <a href="mailto:jason@planet57.com">Jason Dillon</a>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] Created: (JBAS-8326) Invalid dependency in jboss-as-jmxpom
by Martin Höller (JIRA)
Invalid dependency in jboss-as-jmxpom
-------------------------------------
Key: JBAS-8326
URL: https://jira.jboss.org/browse/JBAS-8326
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-5.1.0.GA
Environment: Maven 2.0.10, JBossAS 5.1.0.GA
Reporter: Martin Höller
Assignee: Dimitris Andreadis
The maven module with groupId "org.jboss.jbossas" and artifactId "jboss-as-jmx" has a dependency to jboss-as-j2se. This might be ok. However, the dependency is declared twice, the second time with a type of "test-jar" but not with scope test. This prevents it from beeing used as a dependency in an EAR, as the maven-ear-plugin doesn't know (and shouldn't need to know) how to handle artifacts of type test-jar. It probably should't be packaged in an EAR anyway, but the dependency nevertheless seems wrong.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] Created: (JBAS-8117) Rename folder prefix in distribution zip from jboss to jboss-as
by Dan Allen (JIRA)
Rename folder prefix in distribution zip from jboss to jboss-as
---------------------------------------------------------------
Key: JBAS-8117
URL: https://jira.jboss.org/browse/JBAS-8117
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Dan Allen
Assignee: Paul Gier
We complain that people still refer to AS as just JBoss but you gotta admit that we're not encouraging them not to considering that the AS download is just called jboss and expands just as jboss.
The dist zipfile name (jboss-as-distribution-6.0.0.20100429-M3.zip) is consistent with the renaming. However, when you unzip it, the top-level directory (i.e. JBOSS_HOME) name is "jboss-6.0.0.20100429-M3". Can't we change this to "jboss-as-6.0.0.20100429-M3", or even better to "jboss-as-6.0.0.M3" (I don't think the date is necessary), for future releases?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] Created: (JBBUILD-607) AS testsuite test targets don't work on windows
by Alexey Loubyansky (JIRA)
AS testsuite test targets don't work on windows
-----------------------------------------------
Key: JBBUILD-607
URL: https://jira.jboss.org/jira/browse/JBBUILD-607
Project: JBoss Build System
Issue Type: Bug
Components: Targets and Tasks
Reporter: Alexey Loubyansky
Since we've switched to maven repository classpath for testsuite classpath, the classpath got too long to work on windows.
So, it either has to be shorter or a manifest-only jar can be created that would reference all the jars and dirs.
The problem with the manifest-only jar is that there must be relative path from the jar location to all the other jars and dirs that need to be included in the classpath. Taking into account that the relative path might not exist (e.g. the AS checkout and maven local repo can be on different drives) the jar might not work.
(Although, right now on my windows machine fixed it with generating the manifest-only jar.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] Created: (JBASMP-12) Move JBossAS Maven Plugins into their own tree
by Andrew Lee Rubinger (JIRA)
Move JBossAS Maven Plugins into their own tree
----------------------------------------------
Key: JBASMP-12
URL: https://jira.jboss.org/jira/browse/JBASMP-12
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Currently under maven/plugins/jboss/trunk is:
drwxrwxr-x 4 alrubinger alrubinger 4096 2008-10-21 21:35 maven-buildmagic-thirdparty-plugin
drwxrwxr-x 5 alrubinger alrubinger 4096 2008-09-24 06:10 maven-jboss-as-build
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-common
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:55 maven-jboss-as-control-example
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-control-plugin
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-02 05:34 maven-jboss-ejb3-testrunner-plugin
drwxrwxr-x 4 alrubinger alrubinger 4096 2008-09-15 11:15 maven-jboss-license-plugin
drwxrwxr-x 12 alrubinger alrubinger 4096 2008-10-21 21:49 maven-jboss-surefire
-rw-rw-r-- 1 alrubinger alrubinger 1229 2008-10-21 21:35 pom.xml
Those prefixed with "maven-jboss-as" should be in their own tree
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months