Modify

Ticket #47 (new enhancement)

Opened 4 years ago

Last modified 3 years ago

tool for module management

Reported by: mpo Owned by: mpo
Priority: minor Milestone: 0.5
Component: -- unknown -- Version: trunk
Keywords: Cc:

Description (last modified by mpo) (diff)

The first incarnation of the maven artefact for kauri-projects will create a standard project with one module called 'module1'.

If maven artefacting would allow it would be far nicer to let that module have a dynamic name like "{appname}-main".

Anyway, this current limitation shows another (probably more interesting) general developer-use-case to solve: renaming of existing modules in an ongoing application.

The steps involved are:

  • renaming the directory
  • renaming in the pom's xml (artefactid)
  • renaming in the parent pom referring to this child 'module'
  • renaming in the kauri.xml referring to this module

and possibly even further down in sibling modules there might be references

  • inside classloader-template
  • inside their pom (dependencies)

Attachments

Change History

comment:1 Changed 4 years ago by mpo

  • Description modified (diff)

comment:2 Changed 4 years ago by mpo

  • Description modified (diff)

comment:3 Changed 3 years ago by mpo

  • Milestone changed from 0.4 to 0.5

beyond 0.4 scope

View

Add a comment

Modify Ticket

Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.