Eclipse PDE integration into Maven and unit test failure
--------------------------------------------------------
Key: JBBUILD-357
URL: http://jira.jboss.com/jira/browse/JBBUILD-357
Project: JBoss Build System
Issue Type: Bug
Components: Maven
Reporter: Mark Proctor
Assigned To: Paul Gier
Eclipse plugin building and testing is automated by ant, executed by the Eclipse antRunner.
Inside of Maven we have antRunner called in two different phases. When the test phase has unit test failures, they are not propagated up to maven, so failures are not flagged and a sucecssful build reported. Look in the drools-eclipse module of jboss rules for more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Release plugin doesn't pickup compile plugin configuration from parent
----------------------------------------------------------------------
Key: JBBUILD-470
URL: http://jira.jboss.com/jira/browse/JBBUILD-470
Project: JBoss Build System
Issue Type: Bug
Environment: 4-beta2
Reporter: Carlo de Wolf
Assigned To: Paul Gier
Compile configuration defined in a parent pom does not get picked up by the release plugin during release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Break out Deployment-related Plugins into their own Project
-----------------------------------------------------------
Key: JBASMP-7
URL: http://jira.jboss.com/jira/browse/JBASMP-7
Project: JBoss AS Maven Plugins
Issue Type: Task
Components: control-plugin
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Fix For: 0.1.0
The Control Plugin currently houses Deployment Mojos; these should have their own Plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create "deploy" Mojo for maven-jboss-as-control-plugin
------------------------------------------------------
Key: JBBUILD-478
URL: http://jira.jboss.com/jira/browse/JBBUILD-478
Project: JBoss Build System
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
The JBoss AS Control Plugin currently has Mojos for "createConfiguration", "start", and "stop". We need to add a "deploy" Mojo which delegates to congruent functionality from jboss-test.
Existing Mojos:
http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-as-c...
Root Checkout Location:
http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk
After the "deploy" Mojo is created, configuration to use it should be added to the "maven-jboss-as-control-example" project, following examples already in place in the POM. This is the self-documenting usage project which may also prove its validity.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rename folder structure of modules
----------------------------------
Key: JBASMP-5
URL: http://jira.jboss.com/jira/browse/JBASMP-5
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Modules are currently namespaced with "maven-jboss-as-", which is unnecessary due to the groupId and folder structure. For instance:
maven-jboss-as-build
...should become:
build
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable
-------------------------------------------------------------------------------
Key: JBASMP-8
URL: https://jira.jboss.org/jira/browse/JBASMP-8
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: 0.1.0
Replace all instances of non-Maven Logging code to AbstractMojo.getLog() within the Mojos themselves
--
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
Implement Deltas-only copying of configurations
-----------------------------------------------
Key: JBASMP-4
URL: http://jira.jboss.com/jira/browse/JBASMP-4
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
>From Antony Stubbs:
The other thing I noticed is that the JbossAsControlCreateConfigurationMojo doesn't seem to perform a delta copy as ALR has mentioned in places, but instead copies the entire directory every time and overwrites existing files. Is this a feature worth pursuing? It took quite a long time (at least 60 seconds) copying the config directory on every invoke for me - i.e. it appears worth it to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Change default overlayLocation to src/jbossas/resources
-------------------------------------------------------
Key: JBASMP-9
URL: https://jira.jboss.org/jira/browse/JBASMP-9
Project: JBoss AS Maven Plugins
Issue Type: Task
Components: control-plugin
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
src/main/resources is for application/module resources; move the default for JBossAS Configuration files into their own namespace.
--
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
Review and Commit Patches by Antony Stubbs
------------------------------------------
Key: JBASMP-3
URL: http://jira.jboss.com/jira/browse/JBASMP-3
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Community Contributor Antony Stubbs has provided patched (in linked issue). This task is to track their commits to a release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Align current versions to all start at 0.1.0-SNAPSHOT
-----------------------------------------------------
Key: JBASMP-6
URL: http://jira.jboss.com/jira/browse/JBASMP-6
Project: JBoss AS Maven Plugins
Issue Type: Task
Components: build, common, control-example, control-plugin
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Fix For: 0.1.0
POMs should be set to same version, 0.1.0-SNAPSHOT, including the Aggregator POM
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira