Download all versions of hawkular-accounts-feature-pack-resources JAR files with all dependencies
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.18.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.18.Final
Last update 04. February 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.18.Final
Last update 04. February 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.17.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.17.Final
Last update 29. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.17.Final
Last update 29. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.16.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.16.Final
Last update 26. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.16.Final
Last update 26. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.15.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.15.Final
Last update 26. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.15.Final
Last update 26. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.14.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.14.Final
Last update 25. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.14.Final
Last update 25. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.13.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.13.Final
Last update 25. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.13.Final
Last update 25. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.12.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.12.Final
Last update 22. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.12.Final
Last update 22. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.11.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.11.Final
Last update 14. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.11.Final
Last update 14. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.10.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.10.Final
Last update 06. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.10.Final
Last update 06. January 2016
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hawkular-accounts-feature-pack-resources from group org.hawkular.accounts (version 2.0.9.Final)
This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem
fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module.
Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars.
Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the
subsystem-templates by wildfly-server-provisioning-maven-plugin.
Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.
0 downloads
Artifact hawkular-accounts-feature-pack-resources
Group org.hawkular.accounts
Version 2.0.9.Final
Last update 17. December 2015
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hawkular.accounts
Version 2.0.9.Final
Last update 17. December 2015
Tags: need resources maven have sake from pack plugin kind because although hawkular able solely usually only pulled move jars just module accounts once templates loading here code main projects that fragments inside there exists will subsystem server load wildfly modules some this provisioning hosted
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Page 1 from 2 (items total 12)