[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ]
James Perkins commented on JBASMP-41:
-------------------------------------
Nope, looks like in a CLI script it would work. I suppose you could setup some goals to generate a script file maybe.
> Create goals to add modules do Jboss AS
> ---------------------------------------
>
> Key: JBASMP-41
> URL: https://issues.jboss.org/browse/JBASMP-41
> Project: JBoss AS Maven Plugins
> Issue Type: Feature Request
> Reporter: Gustavo Orair
> Assignee: James Perkins
>
> A command to create modules using Jboss CLI was created
> (refer to https://issues.jboss.org/browse/AS7-4265).
> It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section.
> Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located:
> <execution>
> <id>create-modules</id>
> <phase>install</phase>
> <goals>
> <goal>execute-commands</goal>
> </goals>
> <configuration>
> <execute-commands>
> <commands>
> <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command>
> </commands>
> </execute-commands>
> </configuration>
> </execution>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6948) Login configuration does not work for custom mail server
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6948?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6948:
----------------------------------------------
Tomaz Cerar <tcerar(a)redhat.com> made a comment on [bug 953688|https://bugzilla.redhat.com/show_bug.cgi?id=953688]
Description of problem:
You cannot configure login config for custom-mail server configuration.
This results in not beeing able to connect custom-mail server if it uses authentication
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
<mail-session jndi-name="java:jboss/mail/Custom">
<custom-server name="smtp" outbound-socket-binding-ref="mail-smtp-tls">
<login name="user at gmail.com" password="password"/>
<property name="host" value="smtp.gmail.com" />
<property name="port" value="587" />
<property name="starttls.enable" value="true" />
</smtp-server>
</mail-session>
Actual results:
failed to parse xml configuration / login not working
Expected results:
i can send mail
Additional info:
> Login configuration does not work for custom mail server
> --------------------------------------------------------
>
> Key: AS7-6948
> URL: https://issues.jboss.org/browse/AS7-6948
> Project: Application Server 7
> Issue Type: Bug
> Components: Mail
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> You cannot configure and use login configuration when having custom server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS
by Gustavo Orair (JIRA)
[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ]
Gustavo Orair commented on JBASMP-41:
-------------------------------------
It's great to see a prompt response! Thanks!
For now, would it fail also if I use CLI scripts?
> Create goals to add modules do Jboss AS
> ---------------------------------------
>
> Key: JBASMP-41
> URL: https://issues.jboss.org/browse/JBASMP-41
> Project: JBoss AS Maven Plugins
> Issue Type: Feature Request
> Reporter: Gustavo Orair
> Assignee: James Perkins
>
> A command to create modules using Jboss CLI was created
> (refer to https://issues.jboss.org/browse/AS7-4265).
> It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section.
> Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located:
> <execution>
> <id>create-modules</id>
> <phase>install</phase>
> <goals>
> <goal>execute-commands</goal>
> </goals>
> <configuration>
> <execute-commands>
> <commands>
> <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command>
> </commands>
> </execute-commands>
> </configuration>
> </execution>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-6925) ignore CNFE when scanning for entity classes in deployment
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-6925?page=com.atlassian.jira.plugin.s... ]
Scott Marlow commented on AS7-6925:
-----------------------------------
I would be guessing if I said what is, without checking the classloading code that probably experienced the OOM and threw the CNFE. I guess I do have an opinion on this after all. ;)
This also will help with the case that the deployment contains a class that isn't needed but references other classes that don't exist in the deployment (that is the case that is worth ignoring/logging the CNFE for).
> ignore CNFE when scanning for entity classes in deployment
> ----------------------------------------------------------
>
> Key: AS7-6925
> URL: https://issues.jboss.org/browse/AS7-6925
> Project: Application Server 7
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 8.0.0.Alpha1
>
> Attachments: cnfe.jar
>
>
> Deployments may contain non-entity classes that can not be loaded (see above forum reference for example).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBASMP-42) execute-commands only executes commands that translate into operations
by James Perkins (JIRA)
James Perkins created JBASMP-42:
-----------------------------------
Summary: execute-commands only executes commands that translate into operations
Key: JBASMP-42
URL: https://issues.jboss.org/browse/JBASMP-42
Project: JBoss AS Maven Plugins
Issue Type: Bug
Reporter: James Perkins
Assignee: James Perkins
Commands like {{module add}} do not work in the {{execute-commands}} goal.
See the {{CommandContext.handle()}} on how to execute these commands. Need to look at more details on how this method works and if it will work correctly without a shell.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ]
James Perkins commented on JBASMP-41:
-------------------------------------
This could be done with the {{maven-dependency-plugin}}, but when testing I realized commands are property handled in the plugin. Since the modules command is an actual command and not an operation it fails to create execute. This needs to be fixed first, but it could be more intuitive to have a goal like you suggest rather than relying on the command.
FWIW the config would look like:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.6</version>
<executions>
<execution>
<goals>
<goal>properties</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- JBoss AS plugin to deploy war -->
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>${version.jboss.maven.plugin}</version>
<executions>
<execution>
<id>create-modules</id>
<phase>package</phase>
<goals>
<goal>execute-commands</goal>
</goals>
<configuration>
<execute-commands>
<commands>
<command>module add --name=oracle.jdbc
--resources=${com.oracle:ojdbc6:jar}
--dependencies=javax.api,javax.transaction.api
</command>
</commands>
</execute-commands>
</configuration>
</execution>
</executions>
</plugin>
{code}
> Create goals to add modules do Jboss AS
> ---------------------------------------
>
> Key: JBASMP-41
> URL: https://issues.jboss.org/browse/JBASMP-41
> Project: JBoss AS Maven Plugins
> Issue Type: Feature Request
> Reporter: Gustavo Orair
> Assignee: James Perkins
>
> A command to create modules using Jboss CLI was created
> (refer to https://issues.jboss.org/browse/AS7-4265).
> It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section.
> Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located:
> <execution>
> <id>create-modules</id>
> <phase>install</phase>
> <goals>
> <goal>execute-commands</goal>
> </goals>
> <configuration>
> <execute-commands>
> <commands>
> <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command>
> </commands>
> </execute-commands>
> </configuration>
> </execution>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ]
James Perkins edited comment on JBASMP-41 at 4/18/13 5:55 PM:
--------------------------------------------------------------
This could be done with the {{maven-dependency-plugin}}, but when testing I realized commands are property handled in the plugin. Since the modules command is an actual command and not an operation it fails to create execute. This needs to be fixed first, but it could be more intuitive to have a goal like you suggest rather than relying on the command.
FWIW the config would look like if the command worked:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.6</version>
<executions>
<execution>
<goals>
<goal>properties</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- JBoss AS plugin to deploy war -->
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>${version.jboss.maven.plugin}</version>
<executions>
<execution>
<id>create-modules</id>
<phase>package</phase>
<goals>
<goal>execute-commands</goal>
</goals>
<configuration>
<execute-commands>
<commands>
<command>module add --name=oracle.jdbc
--resources=${com.oracle:ojdbc6:jar}
--dependencies=javax.api,javax.transaction.api
</command>
</commands>
</execute-commands>
</configuration>
</execution>
</executions>
</plugin>
{code}
was (Author: jamezp):
This could be done with the {{maven-dependency-plugin}}, but when testing I realized commands are property handled in the plugin. Since the modules command is an actual command and not an operation it fails to create execute. This needs to be fixed first, but it could be more intuitive to have a goal like you suggest rather than relying on the command.
FWIW the config would look like:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.6</version>
<executions>
<execution>
<goals>
<goal>properties</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- JBoss AS plugin to deploy war -->
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>${version.jboss.maven.plugin}</version>
<executions>
<execution>
<id>create-modules</id>
<phase>package</phase>
<goals>
<goal>execute-commands</goal>
</goals>
<configuration>
<execute-commands>
<commands>
<command>module add --name=oracle.jdbc
--resources=${com.oracle:ojdbc6:jar}
--dependencies=javax.api,javax.transaction.api
</command>
</commands>
</execute-commands>
</configuration>
</execution>
</executions>
</plugin>
{code}
> Create goals to add modules do Jboss AS
> ---------------------------------------
>
> Key: JBASMP-41
> URL: https://issues.jboss.org/browse/JBASMP-41
> Project: JBoss AS Maven Plugins
> Issue Type: Feature Request
> Reporter: Gustavo Orair
> Assignee: James Perkins
>
> A command to create modules using Jboss CLI was created
> (refer to https://issues.jboss.org/browse/AS7-4265).
> It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section.
> Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located:
> <execution>
> <id>create-modules</id>
> <phase>install</phase>
> <goals>
> <goal>execute-commands</goal>
> </goals>
> <configuration>
> <execute-commands>
> <commands>
> <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command>
> </commands>
> </execute-commands>
> </configuration>
> </execution>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months